Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Was it a case of poor scrum implementation or do you feel it just doesn't work?
All attempts for maintenance tasks were ignored and never made it into the sprint. Despite quite loud protests.
Committing to a sprint and all the estimated tasks is impossible when you have to support a released product with urgent bugfixes.
Meetings, endless amounts resulted in never getting into the flow, due to an upcoming meeting in an hour. Devs work best in 3-4 hour slots. Morning to lunch, uninterrupted, and lunch to quitting time. One of these slots can be replaced with a meeting, but not both.
@cheke it seems to be a trend that people don't do it "right". Luckily, most of the world has moved away from this mini waterfall method.
It was so bad the way our scrum master ran it, that even if the PM cancelled a feature - if it was still in the next sprint, he wouldn't allow him to take it out. Because it was already scheduled..
cheke4513yOMG that guy is a legend...sounds like worse ran than the hybrid Kanban that runs in my work currently@viking8