The Problem with Incompetent Scrum Masters: Why Lack of Skills in Team Context Results in Poor ROI

Published on
6 minute read

When organizations invest in Scrum Masters, they expect results. Yet, too often, they find that the promised returns aren’t realized. Why is that? It boils down to a lack of competence within the Scrum Master’s role—particularly in understanding the context of the team, the product owner, and the organizational structure. Without this, the return on investment (ROI) diminishes. Let’s dive into why having a skilled Scrum Master is crucial and how to measure their impact effectively.

Why Competent Scrum Masters Matter

A competent Scrum Master can significantly impact a team’s success. Here’s how:

  • Increased Team Delivery: With a skilled Scrum Master, teams deliver more value. They are better equipped to take calculated risks, leading to more innovation and new opportunities.

  • Enhanced Focus on New Work: Without competent leadership, teams often spend excessive time on maintenance rather than focusing on new developments. A good Scrum Master helps balance this focus.

  • Lower Defect Rates: Competence in modern engineering practices and DevOps means fewer bugs and higher-quality products, which is essential in today’s fast-paced tech landscape.

What Happens Without a Competent Scrum Master?

When a Scrum Master lacks the necessary skills, here’s what you can expect:

  • Less Delivery: Teams may struggle to push out new features or improvements, directly impacting ROI.

  • Higher Defect Rates: Without strong practices, teams may experience increased defects, leading to more time spent on bug fixes rather than innovation.

  • Limited Team Growth: Teams might become comfortable with their pace, leading to stagnation rather than growth.

👉 Remember: Happy teams are essential, but the true ROI comes from delivering valuable products to your customers.


Measuring the Value of a Scrum Master

To truly assess the impact of a Scrum Master, you need to gather data. Below are some key metrics that can help you determine their effectiveness.

1. Innovation Rate: Is Your Team Innovating Enough?

  • Definition: The innovation rate measures the percentage of time your team spends on new functionality versus maintaining or improving existing features.

  • Why It Matters: Higher innovation rates mean your team is adding more value to your product, attracting new customers, and opening new markets.

  • Industry Standard: According to DORA metrics, the average innovation rate is around 29%. This means for every dollar spent, only 29 cents go toward creating new value.

🔍 Example: A major streaming platform like Netflix might compare the development of a new series (innovation) against remastering an existing one (maintenance).

2. On-Product Index: Where Is Your Team’s Time Going?

  • Definition: This measures the percentage of time team members dedicate to your product versus other tasks, such as meetings or organizational activities.

  • Why It Matters: If your team spends too much time outside of product development, you’re not getting the most out of your investment.

  • Industry Insight: Most teams allocate 80% of their time to the product and 20% to other activities, roughly equivalent to one day a week lost to non-productive tasks.

📅 Recommendation: Track this to ensure your team remains focused on value-adding activities.

3. Usage Index: Are Your Customers Using What You Build?

  • Definition: This measures the percentage of product features actively used by your customers.

  • Why It Matters: A low usage index indicates that your team is building features that customers don’t find valuable.

  • Reality Check: According to the Standish Group’s CHAOS report, only about 35% of features are actually used. However, real-world data can often be much lower.

💡 Example: A bank I worked with believed they had an 80% usage rate for their features. But after adding telemetry to track actual usage, it turned out only 8% of features were used.

4. Installed Version Index: Are Your Users Up-to-Date?

  • Definition: This tracks the percentage of your user base using the latest version of your product.

  • Why It Matters: A higher percentage means better adoption of new features and less time spent supporting outdated versions.

  • Industry Insight: A 70% installed version index is common, but it means that 30% of users may not be benefiting from your latest improvements.

📲 Tip: Aim for a higher installed version index to reduce support time and costs.


Calculating the Real ROI: The Harsh Truth

Let’s look at the combined impact of these metrics on your ROI. For every dollar you spend on product development:

  • Innovation Rate: 29 cents of net new value.

  • On-Product Index: Lose 20%, bringing it down to 23 cents.

  • Usage Index: Drops it further, as only 35% of features are used, reducing it to around 8 cents.

  • Installed Version Index: Lowers this to around 6 cents.

🚨 Warning: That’s 6 cents of return for every dollar invested! And this is with optimistic numbers.

Real-World Data: The Importance of Measuring Success

A bank I consulted with discovered the gap between perception and reality when they thought their feature usage was at 80%, but actual data showed just 8%. This was a wake-up call and led to changes in their product strategy.

📈 Lesson: Don’t rely on assumptions—use real data to drive your decisions.


How a Competent Scrum Master Can Change the Game

A skilled Scrum Master can directly influence these metrics by:

  • Boosting Innovation Rates: By facilitating better team collaboration, encouraging experimentation, and focusing on value.

  • Increasing the On-Product Index: Reducing distractions and helping the team maintain focus on delivering value.

  • Improving the Usage Index: Guiding product owners to focus on features that matter most to users.

  • Elevating the Installed Version Index: Encouraging best practices in release management and user adoption.


Measuring Scrum Master Impact: Hold Them Accountable

Your Scrum Masters should be able to demonstrate their impact through improved metrics. If you don’t see improvements over time, it might be time to reconsider your investment.

Key Takeaways: How to Measure and Improve ROI

  • Choose the Right Metrics: Focus on innovation rate, on-product index, usage index, and installed version index.

  • Track Progress: Measure these regularly and adjust your strategy as needed.

  • Hold Scrum Masters Accountable: Expect tangible improvements in these metrics when you hire skilled Scrum Masters.

🚀 Pro Tip: If your metrics aren’t improving, you’ve likely got the wrong Scrum Master for the job.


Conclusion: Competence Is Key to Unlocking ROI

In today’s competitive landscape, a competent Scrum Master can be the difference between a team that merely gets by and one that thrives. It’s not just about having happier teams; it’s about delivering more value to your customers. Measure, adjust, and ensure your investment in Scrum Masters pays off. 👉 Final Thought: Don’t settle for mediocrity. Invest in Scrum Masters who can drive real change and watch your ROI soar.

Having Scrum Masters that have a lack of competence within the context of the team’s work, the product owner’s work, and the organisational structure means that you’re going to be getting less return on your investment. I mean, that’s fundamentally what it is. The team is probably going to be delivering less stuff. It’s probably going to be making fewer bets on new stuff, so you’re probably going to spend less time on that new stuff, and they’re probably going to have higher defect rates, right? Because they don’t have the modern engineering excellence and DevOps practices that are needed to build awesome products in today’s world.

There are absolutely teams out there that are doing this without Scrum Masters, right? I’m not disagreeing with that. I’m saying that if you have a Scrum Master with the capability to help a team maximise those capabilities, then you’re going to be able to vastly increase your ROI for your team. But you need Scrum Masters with those competencies; otherwise, all you’re going to get is teams that are happier with each other, not teams that are able to actually deliver more stuff. Both of those things are important, but delivering more stuff is where your ROI comes in.

What I would want you to do is collect some metrics and use those metrics to measure the fundamental benefit that the Scrum Masters are bringing you, okay? Bang for their buck, right? Here are some examples. I’m going to use an example over here because I have some data around it. I would want to measure innovation rate, which is the percentage of time that your team spends working on net new functionality versus maintenance and support and augmenting existing functionality.

If you’re Netflix, that’s a new series versus a second season of an existing series, right? Or remastering some older series, right? So that’s this measure. I want to measure my on-product index. I want to be measuring the percentage of time that my team members have to work on my product versus having to work on other things. What percentage of time are they actually working on my product?

I want to be monitoring my usage index for my product, so I’m looking at the data around how my users interact with my product, right? That’s a great metric. And then perhaps, if you have an app that is installed, I maintain and support one. You have the installed version index: what percentage of people running your tool are on the latest version of the tool, and what percentage are on older versions of the tool? Because that goes to engineering excellence and various things.

Let’s say you had those metrics. I’m going to tell you the industry standard for each of those metrics, and we’re going to base it on a dollar. And yeah, I’m using US dollar, pound, Euro, whatever you want. For each dollar you spend on your product, what you lose by each of these metrics. The innovation rate is about 29%. That’s the average innovation rate; that’s from the DORA metrics. So for every dollar that you spend on your product, you’re getting about 29 cents of net new value, right? For opening up new markets, for adding new capabilities to your products, 29 cents.

So you’re 29 cents in the dollar, right off the bat. Most teams spend about 80% of their time working on the product and 20% of their time doing other stuff for the organisation. So that could be meetings, all hands, training stuff, right? It’s about, I think that’s about a day a week, isn’t it? Something like that. Anyway, so now you’re down to 23 cents in the dollar because you’ve lost 20%.

What about usage index? What do you think the metric shows? The data that I’ve seen, some of it’s from real customers. The happy metrics are from the Chaos Report from the Standish Group in Boston, and they found that only about 35% of the features that are built are actually used by your customers. Only about 35%, right? That’s because we’re not changing fast enough; we’re not adapting fast enough. 35%. So now we’re down to 8 cents on the dollar.

8 cents on the dollar. Eight out of 100, right? 8 cents return on investment for a $1 input. What the heck? That is terrible. 8 cents on the dollar. And that metric is really optimistic. I did some work with a bank in the US who said that 35% usage index? That’s crap. We know our customers way better than that. We understand they’re using all of our features, or as much as, you know, they’re, oh, we’re 80%, right?

So we said, why don’t we add some telemetry onto your product and let’s see? They are cloud-based products; it was easy. So we added telemetry to the product, we gave it three months, and we looked at the data, and it was about 8% of the features in the product were actually used by their customers. And that was over a year-end. Luckily, we were just in the right time for that, so it was over a year-end. So that was a really good picture: 8%, not 35%. 8% of the features.

So that wouldn’t be 8 cents in the dollar; that would be a lot less. And then let’s say installed version index: let’s say it’s 70%. 70% of your users are on the latest version of your product. Now we’re down to 6 cents on the dollar. Do you even know what your numbers look like? Just those metrics: innovation rate, on-product index, usage index, and installed version index. It’s only four metrics. Go collect them and then measure your progress over time.

If you hire Scrum Masters, they should be able to change those numbers. Your Scrum Masters should be accountable for the effectiveness of the team, and you can measure the effectiveness of the team within the context of a product by some of these metrics. These are not the only metrics; I just picked four, right? Because I have some data around them. Pick some metrics that are product-based metrics, value-based metrics for you as a business, and expect those numbers to improve when you hire Scrum Masters. If they don’t, you’ve got the wrong Scrum Masters.

Metrics and Learning Scrum Team Scrum Master People and Process Scrum Product Development Operational Practices Ability to Innovate Professional Scrum Team Performance Practical Techniques and Tooling

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Slicedbread Logo
SuperControl Logo

NIT A/S

Ericson Logo
Flowmaster (a Mentor Graphics Company) Logo
Boeing Logo
DFDS Logo
ProgramUtvikling Logo
Akaditi Logo
Boxit Document Solutions Logo
Microsoft Logo
Graham & Brown Logo
Brandes Investment Partners L.P. Logo
Slaughter and May Logo
Epic Games Logo
Lean SA Logo
Teleplan Logo
Cognizant Microsoft Business Group (MBG) Logo
Department of Work and Pensions (UK) Logo
Nottingham County Council Logo
Royal Air Force Logo
New Hampshire Supreme Court Logo
Washington Department of Transport Logo
Ghana Police Service Logo
Slicedbread Logo
Graham & Brown Logo

NIT A/S

Milliman Logo
Alignment Healthcare Logo
Boeing Logo