michaela-damm.jpg
blocshop
July 19, 2021
0 min read

Estimating User story points in Agile

Estimating User Story Points in Agile.png

Many teams struggle with estimating in software development. They have to take into account many factors and make realistic appraisals. Product Owners must make estimations that guide the team’s workflow. Of course, most Product Owners try their utmost to estimate with precision. But often estimates fall short. Teams and Product Owners whose estimates prove untrue should not have to work massive overtime or suffer adversity. Estimates are exactly that, an educated guess about how much time and how many resources a project will need. So how do we make Agile estimates accurate?

User Stories are one tool Agile gives us to keep our estimates accurate. User Stories allow teams to describe the development process in simple terms. Teams write User Stories with plain language written from the end user’s perspective. User Stories describe a feature or function in the software development project. Teams work together to write User Stories. Each member offers their expertise about how long a feature or function will take to create.

Read more in our article about User Stories and difference with Use cases.

What are Story Points?

Software development Teams use Story Points to explain the difficulty of a User Story. Story Points act as a quick shorthand for teams to see how challenging a story’s work will prove.  Teams base their Story Points on several factors. These factors include the complexity, effort and risk involved in a certain story. Agile teams estimate Story Points during User Story Mapping.


User Story Mapping is where teams create dynamic visual plans for the software development project. Agile teams don’t write out a linear list of backlog items Instead, the software development team outlines their User Stories with (virtual or actual) post-it notes or index cards. Story Mapping keeps teams focused on the actual needs of end-users.

How do we calculate Story Points in Agile?

To estimate User Story Points, teams consider the following factors:

  • The Story’s complexity

  • The capacity and ability of the team

  • Risks

  • Uncertain aspects of the User Story

  • Story prerequisites

  • Amount of work need to complete the story

How do Story Points differ from hours?

So how do Story Points differ from estimation in hours? Why choose to estimate Story Points rather than by the hour? In traditional waterfall software development, teams estimated their time to finish a project in time. They would give a rough timeline of hours, days or weeks the project would take to complete. Agile teams have found that Story Points work better to explain the actual effort required to complete the work of a software development project.  Agile teams use Story Points to describe the complexity, effort and technical skill necessary to finish their work. Story Points keep teams focused on value and project completion, not on time spent  (productively or not).

Story Points help teams estimate the velocity at which they will work. This is useful for User Story Mapping and Sprint planning. Agile teams can check the number of Story Points and compare with their velocity so they ensure they do not under- or over- commit themselves.

Read more on the topic in the "What is scrum velocity and how do we calculate it?" article.

Agile teams take three steps to estimate Story Points. They use Fibonacci sequence numbers, the Story Point Estimation Matrix and Planning Poker. 

Step 1: Fibonacci Sequence numbers

 The Fibonnaci sequence is a series of numbers where each number is the sum of the previous two numbers: 0, 1, 1, 2, 3, 5, 8, 13, 21. Many Agile teams modify this to 0.5, 1, 2, 3, 5, 8, 13, 21. Using the Fibonnaci sequence to estimate the User Story Points teams work fast and with great accuracy. They do not average their Story Points. Instead, they discuss the work ahead in depth. Teams use Fibonacci sequence numbers instead of linear 1, 2, 3, 4, 5, 6 sequences when they cannot estimate absolute values with precision.  In determining Story Points it’s helpful to show the difference between values. We can see the difference between 8 and 13 more quickly than the difference between 8 and 9. 

Step 2: Story Point Estimation Matrix

Agile teams use the Story Point estimation matrix to show the complexity, risks, uncertainty and difficulty of the User Story. The matrix allows teams to outline at a glance the concrete reality of a User Story, not only how long the work will take to complete.  Story Point Estimation Matrixes usually take the form of a table.

Step 3: Planning Poker

Teams use Planning Poker to agree on Story Point numbers for items on their Backlog. During the Sprint planning meeting, each team member receives a set of cards with the numbers of the Fibonacci sequence. The team then discusses Backlog items. Each team member then privately selects the number they believe represents the Story’s point value. All team members then reveal their cards to each other. This helps build consensus. It also helps team members to express themselves without influence from other team members. 

If the team agrees immediately, wonderful! If not, they should take a few minutes to discuss their choices so everyone can understand them.  By the end of Planning Poker the team should have their tasks laid out in order of priority. If a task is smaller than 0.5 the team can combine it with another task.

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

roro665_depict_a_data_sample_thta_completely_changes_its_form_725a4f20-ea40-4dd1-a68d-5c4327c9bf24_1.png
June 20, 2024

Generative AI used for data conversions and reformatting

How to use generative AI for data conversion, addressing integrity, hallucinations, privacy, and compliance issues with effective validation and monitoring strategies.

DALL·E 2024-05-30 09.37.01 - An illustration suitable for an article about ISO 20022. The scene should feature a modern, sleek representation of the ISO 20022 logo in the center. .webp
May 28, 2024

ISO 20022 Explained: A Comprehensive Guide for Financial Institution Managers

What is ISO 20022? How does it affect companies and institutions in the fintech and banking industry and how to prepare for its adoption? All explained in this article.

DALL·E 2024-05-22 20.55.08 - A detailed and high-quality DSLR photo of a person using a laptop to shop online, showing personalized product recommendations on the screen. The back.webp
May 16, 2024

Key AI Trends in E-commerce and Overview of AI integrations for E-commerce Platforms in 2024

Transform your e-commerce platform with AI tools for personalization, analytics, chatbots, search, and fraud detection. Boost sales and improve customer experiences.

eIDAS mark.png
May 09, 2024

Digital Identity and Payment Services in the EU in 2024: Key Updates

eIDAS 2.0 and PSD3 are set to enhance how digital identities and payment services are managed across the European Union in 2024. Here’s an overview of how each framework contributes to the digital landscape of the EU, what to expect, and how to prepare.

eIDAS 2 in fintech and open banking EU market.png
May 06, 2024

What is eIDAS 2.0 and EU Digital Identity Wallet and how will it change the EU digital market

Learn how eIDAS 2.0 and the EU Digital Identity Wallet will transform digital transactions and identity management across the European Union.

best large language models for ERP systems.png
March 31, 2024

Language Models Best Suited for Integration into ERPs

Four prominent large language models stand out for their compatibility and effectiveness in ERP system processes and automation. See what they are.

PSD3 in open banking Blocshop.png
April 23, 2024

PSD2 vs. PSD3: The Evolution of Payment Services Regulation

What is PSD3 in open banking? See how PSD3 compares to PSD2 and what should banks and fintech businesses do to ensure regulatory compliance in the EU market.

roro665_hands_working_with_a_laptop_in_a_modern_office_there_is_20dca307-c993-4539-99d7-fd5ca264248c.png
April 14, 2024

Enhancing ERP Systems with AI Chatbots

Explore how AI chatbots can transform ERP systems, enhancing efficiency, decision-making, and user interaction.

eIDAS in fintech and open banking EU market.png
April 29, 2024

eIDAS: The regulation helping secure Europe's digital future

See how eIDAS enhances EU digital transactions with secure identity verification, supporting e-commerce and public services across Europe.

hybrid ERPs.png
March 21, 2024

Hybrid ERP: An Innovative Approach to Enterprise Resource Planning

Hybrid ERP is a blend of cloud and on-premise solutions. With expertise in both, Blocshop is uniquely positioned to help you with hybrid ERP development and implementation.

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?

chatgpt-35-limitations.jpg
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.

ai-development-cto-2023.jpg
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.

ai-web-development.jpg
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.

cto-ai-software-development.jpg
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.

build-mvp.jpg
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.

ai-tools-developers.png
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.

web-app-ideas.png
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.