Anthony Mersino is a good friend and colleague of mine, and he asked the following question:
What are the disadvantages of using agile and Scrum?
And it made me think a bit. Not only about the question but what would be the best way to answer it.
At the risk of offending some, I kept thinking of a car. Putting the pollution aspect to the side for a second, cars are inherently good. They’ve provided transportation to humans for well over a century. They’ve also evolved, becoming safer, more efficient, and more intelligent. They’re even beginning to self-drive, which is an exciting development.
But then I think the primary disadvantages (or problems) are not in the cars themselves, but in the users—us. It’s how we use them that’s the more significant challenge. For example, driving recklessly or under the influence. Not maintaining them safely. Or allowing unlicensed/inexperienced individuals to drive them too soon.
And I think the same thing applies to agile and Scrum. The disadvantages are not in them but in how we use them. What are some examples that quickly come to mind?
Half-heartedly using them, not following the “rules,” or lacking the willingness to do the “heavy lifting” but expecting good results.
Leaders and organizations weaponize them to drive and measure team behavior.
They are considered Silver Bullet solutions for organizational or systems dysfunction and challenges.
Using or adopting them when the organizational culture is not ready to adapt to support them effectively.
Adopting them and thinking, "Oh, we’re done, now let’s sit back and reap the rewards.” In other words, missing the “continuous” learning, improvement, and adaptation.
Just as in the car, we need to leverage Agile and Scrum with thoughtfulness, experience, skill, and care. Otherwise, call the tow truck!
Stay agile my friend,
Bob.
Here’s the link to Anthony’s finished article. I think he did a great job of consolidating his own and others thoughts around the topic.