Scrum data points on how to increase Velocity

This past week I had the fortune to be trained on Scrum@Scale, a framework for scaling Scrum, but the creator of Scrum himself, Jeff Sutherland. It's not a prescriptive framework like the some of the others. It's built on true Scrum and it reminded me how a lot of the problems companies face is that they aren't even doing basic Scrum right. So when they do scale, they scale up a broken system. If you start with garbage, you get more garbage.

What's great about training with Jeff is that he has so much scientific data and case studies to back it all up. Several of this studies have proven that you can double velocity, that's right, double velocity by using Scrum patterns for teams.

Here are some of the patterns for doubling velocity:

  • Co-location
  • Small teams
  • Stable teams
  • Dedicated teams
  • T-shaped team members
  • Daily Scrum
  • Interrupt buffer
  • A Ready backlog
  • Fix bugs found within a day
  • All testing completed inside the sprint

All of these have data points and studies and research to back it up. I'll cover just a couple below.

The Impact of Agile Quantified. Rally Software Development Corp. 2015

Dedicated Teams

Let's look at one of the patterns, dedicated teams. According to a study by Rally Software, before they were bought, showed a huge increase in productivity when team members were dedicated. Teams that had members 50% dedicated produced around half as much as when teams had members 95% or greater dedicated.

Small Teams

http://www.qsm.com/process_01.html

If we look at Brook's law on cost and time to deliver based on the team-size. It's a huge difference. Look at the team size of 10 people vs 6, vs 4 and the cost they incur. The Team Size of 6 was able to deliver in twice the time of a team of 10 or 17.

Swarming & Context Switching

Let's just look at one more. Swarming and focusing on one or more projects. 

 Weinberg, Gerald M. (1992) Quality Software Management: Systems Thinking. Dorset House, p. 284.

Weinberg, Gerald M. (1992) Quality Software Management: Systems Thinking. Dorset House, p. 284.

Up to 75% waste from working on 5 projects at the same time. Sure that's a lot. Most people have what, avg of 3? That's still 40% loss! Which causes you to need more people to make up the difference. Save money, less people to do the work in a less time.

There are so many more studies and patterns that increase teams's velocity and reduce the company cost. Proving that implementing Scrum correctly is the only way to get ahead of your competition. As Jeff likes to say. "Change or die". Change the way you do work, or your competition is going to take you out.