In “Scrum is Hard and Disruptive #3—If it ain’t broke…” Todd and Ryan explore how sticking with waterfall could make sense. 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 2nd Statement: “If waterfall suits current needs, continue using it.”
Embracing Pragmatism in Agile
At first glance, this statement might seem to endorse the traditional Waterfall model, often seen as the antithesis of agile methodologies like Scrum. However, Miller and Ripley’s discussion reveals a more nuanced perspective. They argue that if a team is effectively delivering results, keeping customers satisfied, and achieving a high return on investment (ROI) using Waterfall, there’s no inherent need to switch to Scrum.
Defining ‘Needs’ in Your Workflow
A key point in their discussion is the definition of ‘needs.’ Miller and Ripley believe ‘needs’ should be customer-driven and outcome-focused. They caution against defining needs based on internal power structures or rigid control mechanisms. Instead, they advocate for defining needs that prioritizes customer satisfaction and tangible outcomes.
No Scrum Purity Police
One of the standout takeaways from the episode is the idea that there’s no “Scrum Purity Police.” Teams shouldn’t feel pressured to rigidly adhere to Scrum if it’s not the best fit for their current situation. If a hybrid approach or another methodology like Waterfall works well, it’s perfectly acceptable to continue with it. The ultimate goal is to keep winning and delivering value, regardless of the methodology label.
Key Takeaway: Flexibility Over Dogma
Miller and Ripley’s insights emphasize the importance of flexibility in project management. They remind us that the accurate measure of success is not how closely a team follows a specific methodology, but how well it meets its goals and satisfies its customers. Whether you’re a staunch advocate of Scrum or a pragmatic user of Waterfall, the core message is clear: do what works best for your team and your customers.
Final Thoughts
This episode of “Scrum is Hard and Disruptive” challenges us to rethink our approach to agile methodologies and frameworks. It’s a call to prioritize effectiveness and results over strict adherence to any single framework. As Miller and Ripley conclude, “If it’s meeting your needs and you’re winning, keep winning.”
⏩ 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