9 Practices that Haunt Developers Working with Scrum
Why Scrum has a bad name
Scrum promised to be liberating for developers. It should have been a radical shift from the command and control practices that defined many waterfall projects. Scrum is about self-managing teams and sustainable pace. It should be an “ennobling experience” (Agile Software Development with Scrum (Schwaber and Beedle), 2001).
The world is flooded with Scrum Trainers, Agile Coaches, and Scrum Masters that spread this message of self-managing Scrum Teams who determine what they do and by when.
But the reality is very different for many Scrum teams and developers suffer from this. Many feel nothing has changed for the better. In fact, some think Scrum is worse than waterfall.
Here are 9 practices that haunt developers working with Scrum.
Crunch time every Sprint
Before Scrum took over the world of software development, organizations usually used traditional project management methodologies. Often referred to as “waterfall”.
Waterfall projects typically had detailed long-term plans and no feedback loops to inspect the product increments. Waterfall projects typically had a crunch time at the end of the journey. In the last weeks of the project, teams…
