basysKom Toolbox

23 – Agile – Story Points

Story Points will improve the accuracy of your estimations


Improve your estimations and release planning.


Story points are estimating the implementation complexity of a story, rather than the required time. Estimating in story points will improve the accuracy of your release plans, decrease the estimation effort for your teams and the variation in estimates due to external changes.

A widespread technic to estimate in story points is the planning poker. It is a format based on a shared understanding of a story. We at basysKom estimate with story points in the size of 1,2,3,5,8,13,20,40,100. Where 1 is a story with a clear idea and low implementation complexity and a 100 is a story which is super complex and not yet implementable. Stories that are takein into a sprint backlog usually end up in the range of 1 to 8 Story Points.

In a planning poker the product owner presents a story to the team, the team can now talk about the story. After that everyone estimates for them self. Once everyone has an estimation selected the team presents the own estimation to the each other. This is the point where the lowest estimation and the highest estimation need to explain why they decided upon the number. This way you can discover hidden complexity, find unspoken questions and increase the team understanding.





Implementation effort

Roughly 1-2 team hours a week


Agile projects


One of the biggest mistakes is to assume that story points can be directly converted into time. This is not directly the case. Story points are about the complexity of stories to each other. At some point you will get a story point velocity (the team achives an average of X story points every sprint). The velocity is the value you can take to setup an estimation when a certain story can be done.

See also

About the Toolbox

The basysKom Toolbox is a state-of-the-art collection of best practices in agile management and software development and a valuable tool for every kickoff meeting.

These cards can be used during a project kickoff in order to select best fitting good practices from the very start of your project, but also as a reminder during the course of a project implementation. Every card holds a QR code with additional information related to the specific tool, the tools’ applicability, known constraints and additional tips on how to implement it in a project setup.

You can provide us feedback on GitHub.


basysKom Newsletter

We collect only the data you enter in this form (no IP address or information that can be derived from it). The collected data is only used in order to send you our regular newsletters, from which you can unsubscribe at any point using the link at the bottom of each newsletter. We will retain this information until you ask us to delete it permanently. For more information about our privacy policy, read Privacy Policy