# How to estimate sprint velocity when there is a change in story points in scrum

Initially, the Product Backlog contained 350 story points of PBIs. After completing 7 sprints of development, the Product Backlog contains 140 story points of PBIs .

The average velocity is 30 per sprint. So it takes 12 sprints to finish the whole project.

After Sprint 9, your client asks to add a new feature. Your team estimates it is 15 story points. Then, after Sprint 10 the client requests another feature to be added. You estimate the size of that feature to be 9 story points. Assuming your team’s velocity does not change, calculate estimates for the total number of sprints.

Scope will continue to increase at the rate of the average of the increases at the ends of Sprints 9 and 10. It will increase at this rate until the Product Backlog is completely burned down during a sprint.

This is where I find difficult. I am not sure how to estimate number of sprints need in this case. What does increase rate is supposed to mean?

Since this is just a estimation, I don't think difficult calculation is needed, does it?

Any help is appreciated.

• The question doesn't make sense. Scope can expand or contract at any time during a project; it's just not allowed to change during a Sprint in a way that impacts the current Sprint Goal without triggering an early termination. Also, scope and velocity aren't the same things, so just estimate how many Sprints are needed to drain the Product Backlog. See pm.stackexchange.com/a/16376/4271 for one approach to doing this. Dec 7, 2020 at 17:09

This seems like some kind of theoretical question, but I can give a few pointers on how to approach this.

• Velocity (the number of points that can be done in a sprint)
• Backlog size (the total number of points left in the backlog)

The simple formula for "how long until we're done?" is Backlog Size / Velocity. This gives you the number of sprints.

However, you seem to be stuck on "What if new stories keep getting added?".

In this case, you've got a third number:

• Increased scope (The number of new points that are added to the backlog each sprint)

With this extra number, the backlog is shrinking more slowly than it would if there's no scope increase. Essentially, to get the rate of shrinkage, you need to subtract the increased scope from the velocity to get the number of points the Backlog shrinks by:

Backlog Size / (Velocity - Increased scope)

So if you have 140 points on the backlog, you have a velocity of 30 and the increased scope is 12 per sprint, you are essentially burning 30-12 = 18 points of backlog per sprint, so you need a total of 140/18 = 8 sprints to finish up the project.

One of the biggest dangers of Increased Scope is that as it approaches velocity, your total time on the project will skyrocket. For example, if your increased scope rises to 25 points per sprint, then your shrinkage becomes 30-25 = 5 per sprint, and completing the project takes another 28 sprints!

Once it equals or exceeds the velocity, you will never get the project done. This is intuitive to understand; you are generating more work per sprint then you can resolve in that time.

• Hi Erik, The textbook definition of the term "scope creep" is that it means uncontrolled change, but that's not the point of this question. In Scrum the PO controls the scope. If the PO approves of additional PBIs then that is controlled change, not scope creep. The distinction matters since scope creep is almost always a negative thing whereas being adaptive to change is a positive thing: it means the team has the opportunity to deliver more value. Finishing a backlog may even be of no great significance because many software products aren't actually "finished" until you stop using them. Dec 12, 2020 at 10:52
• @nvogel you are very right. Updating the answer.
– Erik
Dec 12, 2020 at 22:09

Since the average growth of the backlog is 12 and the velocity is 30 in this example it looks like the projected end point is 15 sprints. The example seems unrealistic since it assumes a constant, predictable rate of growth - probably unlikely in practice.

This is where a burn up chart can be a more helpful tool than a burn down. A burn up chart shows the change in the target scope separately from the trend line.

http://brodzinski.com/2012/10/burn-up-better-burn-down.html