Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "sprint planning"
-
Manager: Feature C doesn’t work
Dev: We never built feature C
Manager: Nonsense, I remember feature C clearly!
Dev: It’s still in the backlog
Manager: But we had many meetings about it
Dev: Never got put on the board
Manager: Feature C is very important!
Dev: It was never assigned to anyone
Manager: What could possibly be more important than Feature C?
Dev: All the other features you placed on the board and assigned up until now
Manager: Well I need Feature C done asap! It should be top priority!
Dev: Ok then next sprint add feature C to the board and assign it to someone
*Next planning session manager leaves feature C in backlog in favour of other tickets*
*2 days later*
Manager: What is the status of feature C?
Dev: You opted to leave it in the backlog
Manager: BUT IT SHOULD BE TOP PRIORITY!
Dev: …9 -
Today is sprint demo day. As usual I'm only half paying attention since being a Platform Engineer, my work is always technically being "demoed" (shit's running ain't it? There you go, enjoy the EC2 instances.)
One team presents a new thing they built. I'm still half paying attention, half playing Rocket League on another monitor.
Then someone says
"We're storing in prod-db-3"
They have my curiosity.
"Storing x amount of data at y rate"
They now have my attention. I speak up "Do you have a plan to drop data after a certain period of time?"
They don't. I reply "Okay, then your new feature only has about 2 months to live before you exhaust the disk on prod-db-3 and we need to add more storage"
I am asked if we can add more storage preemptively.
"Sure, I say." I then direct my attention to the VP "{VP} I'll make the change request to approve the spend for additional volume on prod-db-3"
VP immediately balks and asks why this wasn't considered before. I calmly reply "I'm not sure. This is the first time I'm learning of this new feature even coming to life. Had anyone consulted with the Platform team we'd have made sure the storage availability was there."
VP asks product guy what happened.
"We didn't think we'd need platform resources for this so we never reached out for anything".
I calmly mute myself, turn my camera back off and go back to Rocket League as the VP goes off about planning and collaboration.
"CT we'll reach out to you next week about getting this all done"
*unmute, camera stays off* "Sounds good" *clears ball*4 -
Why is it most companies think being “agile” simply means “let’s say we do work in two week blocks” but without planning or showcases or reviews, without estimations, with ad-hoc tasks inserted continually, priorities changing, tasks moving to the next “sprint” over and over …
But yes, these companies proclaim they are “agile” and do “two week sprints” when it is nothing more than chaos and rhetoric.6 -
One thing that I've noticed is that devs are the most stupid human beings while doing estimation or planning for the sprint. And I'm a dev too2
-
Some sprint planning sessions, and review planning sessions, are just about PO's browsing Jira for lost tickets.
-
Currently having very funny project lead, who gives on the spot estimates for 9 years old very pathetic quality code having Android app in security domain. Memory leaks, bad practices, typos, CVEs etc. you name it we have it in our source of the app.
Since 5-6 sprints of our project, almost 50% of user stories were incomplete due to under estimations.
Basically everyone in management were almost sleeping since last 7-8 years about code quality & now suddenly when new Dev & QA team is here they wanted us to fix everything ASAP.
Most humourous thing is product owner is aware about importance of unit test cases, but don't want to allocate user stories for that at the time of sprint planning as code is almost freezed according to him for current release.
Actually, since last release he had done the same thing for each sprint, around 18 months were passed still he hadn't spared single day for unit testing.
Recently app crash issue was found in version upgrade scenario as QAs were much tired by testing hundreds of basic trivial test cases manually & server side testing too, so they can't do actual needful testing & which is tougher to automate for Dev.
Recently when team's old Macbook Pros got expired higher management has allocated Intel Mac minis by saying that few people of organization are misusing Macbooks. So for just few people everyone has to suffer now as there is no flexibility in frequent changing between WFH & WFO. 1 out of those Mac minis faced overheating & in repair since 6 months.
Out of 4 Devs & 3 QAs, all 3 QAs & 2 Devs had left gradually.
I think it's time to say goodbye 😔4 -
UUUUUUUUSELES PRODUCT OWNER! "Backlog refinement" .. let's do planning! Who does what next sprint?! What about this epic, how is it coming along?! LOOK AT THE FUCKING BACKLOG! USELESS CUNT!4
-
In a sprint planning meeting, tickets are supposed to be detailed prior right? Right? So why are people asking basic "what are we supposed to be doing in this ticket?" questions in this meeting? I proposed doing these meetings and as soon as the concept got hijacked I knew this was going to happen, but damn it I had hope.
And I am so sick of my product manager not knowing the product. These meetings go so fucking cock-eyed because this woman can't be bothered to know the damn product. At all.3 -
Offshore developer announced today he is off for a month, has ruined my sprint planning. He is the most competent developer I’ve had from that team.
Now shooting myself in the foot so we can still get him back and don’t get stuck with a replacement.3