TL; DR: Essential Agile Failure Patterns — When Noise Interferes with Signal
There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. When Scrum becomes an element of an agile transformation, the following three common essential agile failure patterns prove to be an exceptionally tough nut to crack for any Scrum Master.
Reasons for Becoming a Learning Organization
There are various excellent reasons to become agile, for example, by adopting Scrum:
But the fact is also, that the scope of an agile transformation is often wholly underestimated. That “Agile” is not the quick fix for everything that is going wrong. Each organization has its own set of dysfunctions, and hence solutions dealing with them need to be tailored specifically to that organization. However, there are several essential agile failure patterns common in many organizations, three of which I like to introduce in 7:31 minutes.
1. Is Agile a Fad or a Trend?
The Problem: Parts of the leadership—particularly the middle management—pay lip service at best to the idea of becoming an agile organization. Besides business cards, the business analysts are now Product Owners, not much has changed, except for the inevitable “agile playbook” created by a well-reputed consultancy that the lower ranks are asked to “rollout.”
The Consequences: Remember that probably about 10 % of the member of a social group are change agents, 5-10% are refuseniks pushing back, and 80 % typically comprise the silent majority joining when the dices have fallen. With a lot at stake for management folks, why not wait and see? Maybe, it goes away in a few months?
Leadership is about being the first to explore unknown territory at personal risk, thus being a role model. This wait-and-see approach of the leadership will “earn” support from significant parts of the organization: If the leader is not entirely in, why should I be? And now, everything is either stalling or done by half-hearted measures.
The Solution: Awaken the Alexander the Great in you and be a leader. Show support for the massive task at hand by being present and support the effort in every way possible, for example, by:
2. My Budget, My Feature
The Problem: The organization nominally adapts agile practices but sticks with the old ways of figuring out what is worth building:
The Consequences: Think “Agile PMO,” metered funding, contract negotiations, and servant-leadership by status reports. (Concerning the Manifesto of Agile Software Development, we are back to square one.) Typically, this results in misalignment of efforts at an organizational level and stimulates local optimization initiatives within functional silos.
The Solution: Break up functional silos, consider practices like Beyond Budgeting, create empowered product teams tasked with autonomously solving customer problems, and link bonuses strictly to the organization’s overall progress during the agile transformation.
3. There Is no Failure Culture
A former client of mine, a large utility company, practiced at the time a no-failure approach to promotions: A failed project on your internal record meant you would not take the next step on the career ladder. As a result, everyone played safe, which resulted in short-term orientation as not-failing became more important than innovation. Consequently, the organization was increasingly struggling to attract new (tech) talent when software started eating the world.
Suppose “good” failure is not celebrated as a critical part of the learning process, and incrementalism becomes the name of the game. In that case, the Innovator’s Dilemma, as coined by Clayton Christensen, becomes a more likely fate of the organization. When resilience is a worthwhile goal to achieve, think of Netflix’s chaos monkey, failure needs to be an option.
And failure needs to be openly discussed—without repercussions—so everyone can learn from the case. And as it should be, leaders need to confess first. One approach could “failure nights,” or sharing your wrong decisions from the past openly. For example, see Bessemer Venture Partners’ “The Anti-Portfolio. Honoring the companies we missed.”
Essential Agile Failure Patterns — Conclusion
Shouldn’t it be a low-brainer that solving complex adaptive problems of the 21st century does not work by applying methods from the 1890ies? Apparently, it is not. The Manifesto for Agile Software Development has been instrumental in addressing the systemic issues resulting from clinging to Taylorism that numerous organizations still face today. Nevertheless, the overall progress among organizations has been mediocre at best. It is time to change gears.
How is your organization progressing on its path to becoming a learning and agile organization? Are you experiencing one of the many essential agile failure patterns? Please share them with us in the comments.