Common Methods of Story Points
- The Fibonacci Sequence: This method is a popular scoring scale to estimate story points in Agile Scrum. The Fibonacci sequence does as follows 1,2,3,5,8,13,21, etc. The Higher value assigned to the user story represents greater complexity and effort needed to complete the user story.
- T-Shirt Sizing: This method follows the T-shirt size measures such as Extra-Small, Small, Medium, Large, Extra-Large, 2XXL, etc
- The Doubling Sequence: This is another method used to calculate story points which has numbering sequence 1,2,4,8,16 where the digits double in succession.
- Relative Sizing: Story Points are not an absolute measure but a relative one. It’s about comparing the effort of one task or user story to another.
- Consensus: Teams usually estimate story points collectively using techniques like Planning Poker, where team members discuss and vote on the complexity of a task until a consensus is reached.
Story Points and Velocity in Scrum
Developing a software application or any product requires time and measuring the total time required to complete a specified amount of work requires some metrics. In Agile Scrum development methodology, there are two key metrics namely Story Point and Velocity, used to estimate a piece of work and measure the total amount of work completed in a Sprint.
Table of Content
- Story Points
- Common Methods of Story Points
- Velocity
- Steps in Calculating Velocity
- Uses of Velocity
- Relationship between Story Points and Velocity
- Advanced Techniques
- Conclusion
- FAQ’s
In this article let us discuss Story Points and Velocity in more detail.
Contact Us