September 06, 2021
0 min read

Converting Story Points to Hours: Why Doesn't It Work?


In traditional software development, teams would describe the amount of work they had in hours. But Agile software development teams have a better way. Agile teams use Story Points to estimate the work they have ahead of them. Let’s take a closer look at Story Points and hours, and examine the benefits of Story Points.


Teams using hourly estimation try to give an educated guess about how long a feature or bug fix will take to complete. Often they might do this without a full understanding of the complexity of the Sprint ahead. Agile teams may find that hourly estimation causes trouble for them. If they estimate too many hours and finish early, they look like poor estimators. If they take more hours than the estimate, they look like they lack the skills or speed to work as required. The team may also face scope creep and unforeseen obstacles. All these factors make hourly estimation less than ideal.

Story Points

Agile teams use Story Points as a metric to measure the difficulty of a particular User Story. (We remember that Agile Sprints use User Stories as their base. The Agile Team describes a feature or bug in plain language from the perspective of the end-user. That description is our User Story). Story Points seek to measure at least three categories:

  • The total extent of work

  • The complexity of work

  • Risks and uncertainty

Related post: Use Cases vs. User Stories: relationships and differences

How do you convert story points to hours?

Some more traditionally-minded organizations might allow teams to estimate in Story Points and then ask them to convert this into hours. Doing this is worse than comparing apples to oranges. It’s more like comparing a smartphone to a car. Agile Teams create Story Points to give measure to work needed. By meeting with the whole team, including junior and senior developers, they estimate their Story Points. 

The same story point might take one developer eight hours and another developer four hours. Agile teams set Story Points based on relative difficulty. Story Points are by their nature abstract measures. Teams use Story Points because they allow team members who work at different speeds to estimate and collaborate. The team members can agree that a User Story might take twice as long as a previous and similar Story. They then assign a value double the first one Story. So it’s not a discrepancy of several hours depending on who works on the task, but a Story Point that measures comparative difficulty.

When the organization asks the team to convert Story Points to hours, they lose the benefits of using a conceptual calculation. While abstract, Story Points carry meaning and weight that we cannot force into an hourly estimation

However, if the team works for an external client a hybrid method functions, albeit not ideally. Clients may find it difficult to understand why Agile teams prefer Story Points over hours. The team could use a hybrid approach, where Story Points correspond to a rough number of hours. This approach proves less than ideal, though clients may find it easier to understand. 

When developers estimate in hours they might fall short or overshoot their target. Neither way works well for clients or for the team. 

Why are Story Points better than hours?

Savvy Agile teams use Story Points to compare features in the current project with similar features from previous projects. Then the team gains a better understanding of exactly how much work they need to accomplish. The team members then give a value to the Story Point based on the complexity of the task. If the team does not have previous projects, they create a Base Story and Estimation Matrix.

Let’s examine the main benefits of using Story points over hours:

  • Story Points are flexible

  • Teams track Velocity

  • Story Points work better at high-level estimation 

  • Teams do not have to re-calibrate their estimation if Velocity changes

Agile teams like to use Story Points estimation because Story Points use Velocity. Velocity helps them plan for capacity. Velocity allows them to work faster when possible. Team members spend time discussing how to improve their Velocity and work more efficiently in the Sprint Retrospective. Velocity is changeable during projects and Sprints. By using Story Points, the team doesn’t have to change their estimate if Velocity changes. If they were to estimate with hours the story would be very different. 

Story Point Pros and Cons



The entire team helps with the estimation

Clients can have difficulty understanding Story Points

More collaborative, less finger-pointing at slower-working developers

Sharp learning curve, teams may need several Sprints to estimate Story Points with some precision

Less worry about the clock and the calendar

Tasks examined closely, the difficulty of work easy to see

Teams estimate based on abstract measure, not specific developer’s speed or skill

Hourly Estimation Pros and Cons



Good for smaller projects where the team understands the task completely

Highlights the weakest or slowest developer

Velocity is not important to estimate

Hourly estimates link directly with a specific developer

Clock and calendar watching create tension and stress for the team

Hourly estimates prove unreliable 

Here at Blocshop, we take full advantage of Story Points to prioritize our work. We believe the power of Agile gives us an advantage when it comes to software development. We work fast and under budget because we plan and estimate fluently. If you’d like to learn more about how Blocshop can help you with your software development project, please do get in touch!

Learn more from our insights

0-4 cover.png
October 03, 2023

IT Staffing: Individual Hiring vs. Specialized Developer Teams

Should you hire individual developers or go for a specialized, custom-built developer team?

July 17, 2023

ChatGPT-3.5: An Overview and Limitations

In this article, we'll take a closer look at the capabilities and limitations of ChatGPT-3.5, providing you with a comprehensive overview of what it can do and what its boundaries are. So, let's delve into the inner workings of this large language model.

gpt4 vs gpt3-5 and the key differnces.png
June 15, 2023

A Deep Dive into GPT-4 vs GPT-3.5 Differences and Ability to Revolutionize Software Development

There are key differences between ChatGPT-3.5 and ChatGPT-4 that software developers and companies procuring software solutions alike should be aware of. Let's see how these differences affect the output generated by these models on specific examples.

May 09, 2023

AI-powered software development: What CTOs need to know in 2023

As technology continues to evolve at a rapid pace in 2023 and beyond, CTOs must stay ahead of the curve by utilizing predictive analytics, automated testing processes, and deployment solutions.

May 05, 2023

How Artificial Intelligence is changing web development

AI technology is now being used in many different industries, including web development. It’s important to understand the impact that AI can have on web development as it can help companies to create more efficient and user-friendly websites.

May 05, 2023

How AI-powered software development is changing the role of the CTO

As AI-powered software development becomes increasingly commonplace, CTOs must prepare themselves to take on a new set of responsibilities that require more than just technical know-how.

April 17, 2023

How to build a minimum viable product (MVP)

The MVP is the version of a new product that allows Blocshop and your team to collect the maximum amount of validated learning about customers with the least amount of effort. The essence of your core idea is delivered as a barebones solution. The solutions is, however, sufficient for usage by early adopters. As a product, it has tangible qulities that express a look and feel.

March 21, 2023

10 AI tools for developers you should know about in 2023

For developers, programmers, and data scientists, AI coding solutions can free up thinking time, allowing such professionals to focus on the fundamentals of their projects, and complete such projects much faster.

February 14, 2023

17 Ideas for Web Apps in 2023

Gazillions of web apps and ideas for web apps are floating around the metaverse - so creating one that properly represents a unique brand is a huge challenge. Our list provides a number of areas of simple app ideas to help businesses transform their online presence through a web app.

Top 15 micro-SaaS ideas for your startup in 2023.png
December 06, 2021

Top 15 micro-SaaS ideas for your startup in 2022

What exactly do we mean by micro SaaS? Micro Saas solutions use a web browser or mobile app interface. Micro SaaS solutions usually come about through the effort of an individual or very small team. It aims to solve precise problems. Micro SaaS projects have small budgets and overhead. Customers use Micro SaaS solutions on a monthly or yearly subscription basis. Micro SaaS projects target a small niche of the consumer market.

Software engineer hourly rates in 2021 (based on experience and location).png
November 22, 2021

Software engineer hourly rates in 2022 (based on experience and location)

Region influences salary more than any other factor. Taxes rates, cost of living, and government benefit programs affect the rates software developers charge. Software developers in the USA  and Canada earn more than software developers in other countries.

The best programming languages for app development in 2022.png
November 15, 2021

The best programming languages for app development in 2022

Software developers usually have three main ways to create an app. They can choose to code a native app, a hybrid app or a progressive web app. Developers create native apps to function on one specific platform, usually either iOS or Android. They create these apps using Swift or Objective C for iOS. For Android they use C++, Kotlin or several other languages. 

Cross-platform mobile app development: Tools & frameworks for 2022.png
November 09, 2021

Cross-platform mobile app development: Tools & frameworks for 2022

The cross-platform development project aims to create apps compatible with several operating systems. Cross-platform apps work on iOS, Android, and Windows. Cross-platform apps look and feel like apps developed specifically for the operating system.

App development cost breakdown in 2022.png
November 08, 2021

App development cost breakdown in 2022

Your business needs an app, but you aren’t sure about the cost of creating an app. Without some figures, you can’t even begin to estimate the potential budget, so let’s get you sorted with the information you need to make your app a reality.

November 04, 2021

Web app development: a detailed guide

The best web apps give a responsive and engaging user experience through a browser instead of a single application. Think of web app development as a super-charged website. Web apps have many features of mobile apps coded for iOS or Android without the need to code for specific platforms. Developers create web apps using HTML, javascript, Python and CSS.

15 useful web app development tools for 2021.png
October 29, 2021

15 useful web app development tools for 2022

Web development vs app development: Choose the best for your business.png
October 19, 2021

Web development vs app development: Choose the best for your business

Outsource web development in 2021 and beyond: benefits & tips.png
October 15, 2021

Outsource web development in 2021 and beyond: benefits & tips

8 IT outsourcing trends in 2022.png
October 11, 2021

8 IT outsourcing trends in 2022

More and more firms choose to outsource their IT operations and functions. IT outsourcing grows each year. The Gartner report announced that firms spent $3.8 billion dollars on IT outsourcing in 2019. They expect that the trend will continue. Companies aiming for digital transformation need partners and tools. They need tools that they cannot build in-house with speed and accuracy. 

In-house development vs outsourcing software development.png
October 01, 2021

In-house development vs outsourcing software development

Every business starting software development must ask themselves what will serve them better, in-house or outsourcing? There is not a simple answer to the question. Making the choice to develop in-house or to outsource will have long-term consequences.