Story Points 101Converting Story Points to Hours: A Practical Guide for Agile Teams
12th Nov 2024

Converting Story Points to Hours: A Practical Guide for Agile Teams

Now that we have covered Story Points and Velocity, we can apply those concepts and answer questions such as :

  1. When can you deliver feature A?
  2. What can you deliver before the end of next quarter?
  3. Can we get feature A delivered before the end of next quarter?**

Suppose our team's velocity is 30 story points every two-week sprint. Then, in four weeks, they will complete approximately 60, in six weeks, 90, and so on. If the team has five members and one member is away during a sprint, the velocity drops to approximately 4/5 * 30 = 24.

Now we can answer questions about when and for how long the work we are planning will likely take:

Question 1: When can you deliver feature A?

This is a fixed-scope, variable-time question. During development, the team's velocity will always vary a bit. The green and red lines show variability in the number of story points completed in each sprint.

So, looking at the image, having a fixed scope question, when a certain number of story points are delivered, the answer is most likely in the following range:

  • x gives the best-case scenario
  • y gives the worst-case scenario

Question 2: What can you deliver before the end of next quarter?

This is a fixed-time, variable-scope question. Looking at the image, having a fixed time question, we can see that, most likely, the team will

  • Complete all stories below x
  • Some of the stories between y and x
  • None of the stories above z

Question 3: Can we get feature A delivered before the end of next quarter?

This is a fixed-time, fixed-scope question, meaning both the deadline (end of next quarter) and the work required (Feature A) are set.

Using the velocity-based forecast (illustrated in the image), you can determine if the team is on track:

  • If “x” (the projected completion point) falls outside the green and red lines, it indicates that Feature A is unlikely to be completed on time.

This is a fixed-time, fixed-scope question. Looking at the image, if x is outside the green and red lines, the team will most likely be unable to deliver feature A in time.

Best Practice: What to Do If the Forecast Shows a Delay?

When facing a fixed deadline and scope, there are only three viable options:

  1. Extend the Timeline – Push back the deadline to allow the team more time to complete the work.
  2. Reduce the Scope – Remove or simplify features to fit within the available time.
  3. Use a Combination of Both – Adjust both time and scope to find a workable balance.

None of these options include "work harder." Someone might be tempted to say, "Well, you just need to put in longer hours!" If this is common where you work, consider finding another place to work. Why? Because it is a recipe for disaster, as can be seen from these experiences:

Watch Henrik Kniberg explain these concepts

Henrik Kniberg covers these concepts in his excellent video "Agile Product Ownership in a nutshell." The discussion on estimates starts at 11:28.

Decorative image
Share with a friend

Explore More Ways to Improve Delivery

Flow Intelligence

Predictive Planning Poker