- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
You must log in or register to comment.
Estimate the feature high level but with a 1-hour margin of error
Oh my god so much this. “You said it would take roughly 16hours to implement, it’s now 1 hour into the following morning why isn’t it rolled out to production yet?” Or “You estimated 8 hours, it only took 5” “which you’re pleased with?” “No, now we have 3 hours of un-allocated time on this contract which has upset the client”
No, now we have 3 hours of un-allocated time on this contract which has upset the client
I hate this so much. I got told to work slower once and argued back that they should be more confident and sell contracts based on deliverables, not time and materials.
Bingo of Awful IT Processes
A call to discuss calls
4-hour planning
Invited to groom a task, but there are no requirements
QA is not needed: just write code without bugs
These 20 tasks are needed very urgently
Story points = hours
Timetracker
Let’s squeeze the quarterly plan into the sprint
No time for refactoring and technical debt
Estimate the feature high-level, but with a 1-hour margin of error
Finished the feature? It’s not needed anymore, remove it
But this is a simple task. Is it difficult for you or something?
Unregistered overtime
Daily standup for near 1 hour
Let’s quickly discuss this verbally with the whole team
Cutting costs, increasing involvement non-materiallyFinished the feature? It’s not needed anymore, remove it
i didn’t realize that this gave me emotional scars until i winced at reading it just now. lol
