Skip to main content

Scrum Myth: Scrum projects are faster and cheaper

February 14, 2017

The myth I am debunking in this post is that Scrum projects are faster and cheaper.

This myth is my favorite.  There are three challenges with this myth.

  • First, it misses the point of Scrum.
  • Second, it sets teams up for failure.
  • Third, it's impossible to prove.

I assert that there is a bit of truth in this myth.  However, it's not as simple as saying Project X will be cheaper and faster if we use Scrum to deliver it.  Let me explain.

#1 - Missing the point of Scrum.

Untitled design

Scrum is about frequent delivery of working software.

Scrum delivers small, additive pieces of software.  At least every Sprint, we will have a potentially shippable Increment.  This frequent cadence is what enables business agility.  We have the opportunity to start earning return on investment (ROI) faster.  We can also change direction to take advantage of new opportunities.

Scrum focuses on delivering value.

The Product Owner is accountable for optimizing the value of the product.  We don't want to spend money and time on functionality that does not have high enough value.  The iterative-incremental nature of Scrum gives us feedback and tests our assumptions about value.  And if necessary, we can change direction before investing too much in something that does not provide expected value.

And at the end of the day...

If you are delivering stuff that users don't want, it doesn't matter how fast or cheap you deliver it.

Scrum gives the business more flexibility with investment decisions.

In traditional delivery models, the business funds a chunk of fixed scope up front.  The team builds software until all of the scope is complete and/ or the money is spent.  (The latter often involves a painful change request process to get more money.)

Scrum provides transparency to progress and value as functionality is delivered each Sprint.  The business can choose to keep investing in an initiative or not based on the progress they see and the value delivered.  Scrum helps stop the mentality that you should spend all of the money you're given when a project gets funded.

Scrum focuses on quality.

The Definition of "Done" is the bar of quality and completeness in Scrum.  We do not cut quality to deliver something faster or cheaper.  In fact, we seek to increase quality over time through the inspect and adapt cycles of Scrum.

If you are delivering stuff that doesn't work or makes the product brittle, it doesn't matter how fast or cheap you deliver it.

Scrum helps reduce waste.

You can argue there may be cost savings if the team is focused on a goal, and they do not have lost productivity due to context switching.  There may be cost savings if the team is not battling technical debt and suffering from low morale.

But this first requires an investment in quality and continuous improvement.  Teams need time to learn to work together effectively.  Technical excellence takes time and money.

I choose effectiveness over efficiency when it comes to product development.

#2 - Setting teams up for failure.

Belief in this myth sets teams up for failure because management is focusing on the wrong thing.  They may use velocity to measure the performance of a team or individuals.  There may be pressure to fix scope, schedule, and cost.  This undermines team ownership and can lead to some unhealthy behaviors that impact transparency and much more.

The focus should be on empowering and enabling high performing teams.  The focus should be on removing impediments.  The focus should be on measuring value and figuring out what is valuable.

This myth can also be used to justify cutting budgets and giving teams less to work with.

# 3 - Impossible to prove.

Why do I think it's impossible to prove one delivery approach is faster or cheaper than another?

Software development is complex.  Every software development project is unique.  So in order to compare two different approaches, you would need to have the exact same group of people with the same experiences, skills, and personalities working on the same project at the same time in parallel universes.

In summary...

Scrum done well can help companies invest their money more wisely based on empirical evidence.  Scrum done well can help companies get software in the hands of users and customers sooner, which means a faster ROI.

If you've worked on an effective Scrum Team, you know that software development can seem faster and cheaper.  And that is a welcome side effect.  But faster and cheaper is not the value proposition of Scrum.

It's about high value, quality, frequent delivery, and fast feedback.

What did you think about this post?