BROADCASTS.com

This week, Dan and Sam are answering another fascinating listener question. This listener wrote in, \u201cWe are in an organization that has been going through an Agile transformation. Our leaders have been asking for metrics to compare Waterfall vs. Scrum. They want to know if we are delivering more with Scrum. How do we measure this?\u201d

\xa0

Navigating how to measure values when transitioning from Waterfall to Scrum can be a difficult challenge. How do you measure whether something is a successful initiative or not? What are the key differences in what metrics you should be measuring between Waterfall and Scrum? How do you measure the value that Scrum brings? What are some of the key metrics you should be measuring? Tune in to find out!

\xa0

If you have a question of your own (or would like to share your thoughts on today\u2019s episode), you can email the podcast at Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

\xa0

Key Takeaways

How do you measure the value your organization gets from Scrum vs. Waterfall?

Typically what is measured in Waterfalls is \u201ciron triangle\u201d stuff (i.e. \u201cWere we on time? Did we stay on budget? Did we complete the scope?\u201d) However, these things don\u2019t really indicate whether or not you are actually getting value out of the effort

\u201cToo often, what we\u2019re actually measuring in Waterfall was: \u2018Did we get all the work done in a certain amount of time and within budget?\u2019 And that\u2019s not what we\u2019re interested in, in [an] Agile effort.\u201d \u2014 Sam Falco

Find different ways to measure the value, whether it\u2019s in actual dollars earned or cost savings or goals achieved

It is more important to measure the return on investment and the value it brought to customers rather than \u201cDid we push it across the finish line?\u201d

Measure based on value rather than on velocity

It\u2019s not uncommon for those from a Waterfall world to measure how many tasks were completed rather than delivering valuable increments (which is critical with Scrum)

Regardless of whether it is Waterfall or Scrum, you might measure: generated revenue, saved spending, etc.

Evidence-based management as a method for measuring the success of an Agile effort:

Reference The Evidence-Based Management Guide from Scrum.org

It will provide you with a number of key value areas to help determine whether you are actually adding value, as well as some suggestions for key value measures for each of those areas

Listen to episode 107 of the Agile Coaches\u2019 Corner, \u201cEvidence-Based Management 101 with Sam Falco\u201d

Think about the metrics you have in place now and whether or not they apply now (i.e. \u201cDoes this metric we\u2019re using help us determine the current value for our products?\u201d, \u201cDoes it help us determine time-to-market?\u201d, \u201cDoes it help us determine our ability to innovate?\u201d And if not, ask, \u201cDo we really need it?\u201d, \u201cAre we measuring something that matters and drives results?\u201d)

Measure lead time (if it shrinks dramatically, this is a good sign that this is going to work for your organization)

\u201cTake a look at what metrics you\u2019re measuring now. And if those were valuable in telling you whether or not your efforts were worthwhile, they might be appropriate now.\u201d \u2014 Sam Falco

Even though your process is different, you can still measure using a lot of the same metrics \u2014 you just have to look at them in a different way

The most important things to measure are around the value (\u201cIs the stuff we\u2019re producing actually valuable to people?\u201d)

What are some of the ways we can measure value?

Quality metrics (Has your quality increased?) \u2014 Agility tends to come with increases in quality because of a limit of work-in-progress and helping the teams focus

Look at trends; not single points in time

Have your escape defects gone down? Has your technical debt gone down?

Look at things like, how long does it take you to get a release ready for production? Is it taking less time?

One of the values of an agile way of working is that you build in feedback loops for looking at your own processes more frequently than Waterfall

Through this, analyze trends and track process improvement\xa0

There is no single way to measure output from Waterfall to Scrum

You have to always be aware of what the metric is actually telling you and evaluate not only your processes but whether you are using the right metrics (and whether they are telling you things that are helpful to you)

Releasing in Waterfall tends to be infrequent, painful, and fragile. Releases should be frequent and near-automatic in Scrum. Measuring the pain of releasing is an indicator of how easy or difficult it is to capture value

Measure deployment frequency (\u201cHow often do you actually deploy to production or customers and users?\u201d)

Measure: \u201cAre customers happy with the number of releases? Are they happy with the features they\u2019re getting?\u201d

Measure \u201cmean time to first failure\u201d \u2014 though it is an old metric in software development, it can still be valuable (i.e. \u201cHow long does it take for you to break something?\u201d This should be getting longer and longer as your quality goes up)

Keep track of process improvements

\xa0

Mentioned in this Episode:

Evidence-Based Management Guide | Scrum.org

Agile Coaches\u2019 Corner Ep. 107: \u201cEvidence-Based Management 101 with Sam Falco\u201d

The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers, by Ben Horowitz

\xa0

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!