Scrum and the Myth of “Twice the Work in Half the Time”
I often find myself reflecting on the phrase, “Scrum allows you to do twice the work in half the time.” It’s a catchy tagline, isn’t it? One that seems to promise a miraculous transformation in productivity. But let’s be honest, this is more of a marketing gimmick than a reality.
The Reality of Scrum
When we talk about achieving “twice the features in half the time,” we’re not just discussing a simple increase in output. In fact, if we were to break it down, we’re looking at a staggering 400% increase in output. But here’s the catch: Scrum is not about output; it’s about outcomes.
- Output vs. Outcome:
- Output refers to the number of features or tasks completed.
- Outcome focuses on the value delivered to the customer.
Imagine delivering ten features that provide a hundred times the value. That’s the real goal of Scrum. It’s not about churning out more stuff; it’s about delivering meaningful results that truly benefit the end user.
The Damage of Misleading Phrases
This misleading phrase has, unfortunately, done a disservice to our industry. It creates unrealistic expectations and can lead to frustration when teams fail to meet these inflated promises. I’ve seen it time and again, teams under pressure to deliver more, faster, only to find themselves overwhelmed and disillusioned.
Woody Zuill, in his insightful writings, touches on this very topic. He highlights the absurdity of Agile books touting “best practices.” In the Agile world, there’s no such thing as a one-size-fits-all solution. What we have instead are emergent practices that evolve based on the unique context of each team and project.
Marketing vs. Reality
Let’s face it: publishers aren’t going to sell a book titled “Adequate Practices.” They want something that grabs attention, something that promises results. So, we end up with titles that can mislead rather than inform.
Despite this, I’ve found value in leveraging these books, particularly when working with leadership teams who may be sceptical about Agile methodologies. The cover may be flashy, but the content often provides a gateway to deeper conversations about the principles of Scrum.
A Personal Anecdote
I’ve even taken it a step further. I keep a box of these books handy, and I’ve been known to leave them in strategic locations, like near executive bathrooms or in waiting areas. It’s a subtle nudge, encouraging leaders to pick them up and engage with the material.
One book that stands out is one that discusses the Udo Loop and shares compelling stories from Jeff Sutherland’s experiences as a fighter pilot. These narratives resonate and help bridge the gap between scepticism and understanding.
Focus on Value, Not Volume
At the end of the day, we need to shift our focus from output to outcome. It’s not about delivering twice the features; it’s about delivering twice the value, even if that means cutting down on the number of features we provide.
In conclusion, let’s move away from the myth of “twice the work in half the time.” Instead, let’s embrace the true essence of Scrum: delivering value through collaboration, transparency, and continuous improvement. That’s where the real power of Agile lies.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
The Fallacy of Equating Agility with Speed: What Agile Really Means
Explains why Agile is not about speed but about prioritising valuable work, adapting to feedback, and avoiding wasted effort to deliver …
Ditching the Myth of Special Sprints: Embrace True Agile Practices for Usable Products
Explains why relying on special Sprints undermines Agile, and advocates for continuous improvement, accountability, and delivering usable …
Unmasking Agile: How to Spot Genuine Practices Amidst the Myths
Learn how to identify authentic agile practices, spot common myths, and understand cultural barriers that hinder true agility in modern …
Scrum is like communism, it doesn't work. Myth 2
Explains why story points are often misunderstood in Scrum, clarifies their intended use, and offers practical advice for more effective …
Debunking the Top 5 Myths About Scrum: Unlocking Agile Success in Your Organisation
Explores and corrects common misconceptions about Scrum, clarifying its true principles, events, planning, and governance to help teams …
Scrum Myth Debunked: Unfinished Work is Allowed in Scrum
Clarifies Scrum guidelines on unfinished work, explaining that items can span multiple Sprints if the Sprint Goal and Done Increment remain …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.