Here’s Why Many Developers Hate Scrum
And what you can learn from this
Scrum is a disruptive framework. Complex environments need a different approach to build products, taking small steps and inspect and adapt regularly. 34 years after its inception, it still causes confusion and frustration. Many have written books and articles to explain Scrum where they focus on how the framework works, the roles and the Scrum Values.
This information hasn’t convinced all members of Development Teams. Some see Scrum as a burden and “just want to code”. In this article, I am going to show you why they have a point and what you can learn from their issues.
“Just let me code!” — A common response of a developer to the burdens of Scrum
Scrum comes with a lot of new responsibilities
Many embrace Scrum because it empowers the people who create the product. The Development Team manages its capacity and controls how it builds an Increment. The team also determines when Product Backlog Items are “Done”. In Scrum, no-one can tell them to cut corners on quality.
But with autonomy comes responsibility. In Scrum, Development Team responsibility comes in spades.
