Skip to main content

Scrum is Hard and Disruptive #5 - I'm All In

September 13, 2024

In "Scrum is Hard and Disruptive #5—I'm All In" Todd and Ryan discuss why partial implementations of Scrum often do more harm than good. Based on Ken Schwaber's 2006 white paper, this conversation unpacks crucial Scrum aspects that resonate even in today's dynamic business landscape.

Ken's 5th Statement:  "Whenever an enterprise modifies or only partially implements Scrum, it is hiding or obscuring one or more dysfunctionalities that restrict its competence in product development and management." 

 

 

Enterprises that modify or only partially implement Scrum end up hiding their most critical dysfunctions. Instead of embracing the entire framework, many organizations adopt a “Scrum but…” mentality—like using Scrum without letting Scrum Masters do their job or having extended “Sprint Zero” phases dedicated to gathering requirements. These deviations obscure underlying issues, making it difficult for teams to improve.

Scrum isn’t designed to fix problems directly; it’s a framework highlighting where you’re struggling in product development. It gives teams frequent opportunities to inspect and adapt, exposing inefficiencies and opening pathways to better decision-making. However, when organizations cherry-pick which parts of Scrum to follow, they often miss out on these benefits, and their ability to innovate suffers.

Todd and Ryan emphasize that the role of the Scrum Master is crucial here. A true Scrum Master is more than just a facilitator—they are change agents who bring attention to dysfunctions and drive the team toward improvement. This isn’t an entry-level role but one that requires significant experience and leadership. A great Scrum Master doesn’t just point out problems; they actively work with the team to solve them, creating a culture of continuous improvement.

So, if you’re using Scrum but aren’t getting the desired results, ask yourself: Are you genuinely implementing Scrum, or are you hiding behind half-measures? The answer could be the key to unlocking your team’s full product development and management potential.

Ready to commit to Scrum? Dive in fully, confront the dysfunctions, and watch your team’s competence soar. Scrum is hard, but that’s what makes it so powerful.

 

Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 

Check out their books: 

📖 "Unlocking Business Agility with Evidence-Based Management: Satisfy Customers and Improve Organizational Effectiveness" on Amazon -- https://amzn.to/4690qJy 

📖 "Fixing Your Scrum: Practical Solutions to Common Scrum Problems" on Amazon -- https://amzn.to/46dAQTC


What did you think about this post?