Scrum Doesn’t Have to be a Cancer
This is not an article to defend Scrum. There are other people who are more qualified to do that. This piece is purely my opinion, not as a Scrum Master, rather as an Agile practitioner with sufficient experience in doing Agile.
In short, Scrum is not a cancer, but I can’t deny the fact that it can grow into one. I’ve experienced it myself with my own misconceptions about Scrum. Those misconceptions led to unnecessary complexities in implementing Scrum.
Story points are not part of Scrum, including the part where we have to use t-shirt size or any other measurements for that matter. Scrum doesn’t mention anything about Planning Poker or even stand-ups. Those things, and probably many other things, are not elements of Scrum.
Scrum, at its core, is designed to be simple and lightweight. It is providing a structured framework for teams to deliver value iteratively and adapt to changing circumstances. Implementation of Scrum should also be simple and lightweight, not the opposite.
Unfortunately, over time, there has been a tendency for various practices and techniques to be added to the Scrum framework. They were often added in the name of improving its effectiveness. The down side of that is it can lead to unnecessary complexity and unintended consequences.
It’s important to understand that while Scrum allows for additional practices and techniques to be used, these should be evaluated critically. Additions should align with the Agile values and principles. It should also genuinely contribute to the team’s ability to deliver value and work effectively.
If added practices start to burden the team or shift the focus away from Agile, reconsider! If certain practices are not providing value or are causing more harm than good, adjust or remove them! The goal is to find a balance between the core Scrum elements and any additional practices that make sense for the team.
So, while Scrum itself isn’t the problem, its potential complexity can be. It’s our responsibility to stay in line with Agile values and principles while adopting or adapting Scrum. In doing so, we should get the benefit of Scrum without letting it grow into something that inhibits or impedes progress.
