Evaluating the Pros and Cons of Story Points
Over the past two weeks I have decided to better evaluate my personal bias against using story points for estimating. I am personally not a fan as I find them to be very time consuming to get, and very inefficient. Many years ago a fellow agile leader did an analysis of a teams usage of story points and found in many case that 5 point stories were taking double the time of 8 point stories. To help eliminate bias - I have gone back to ChatGPT to evaluate the research and show the pros and cons. I have intentionally asked ChatGPT to share both pros and cons (I also had it write an article purely showing the cons just to see how to alter the response). Please enjoy!
------
Agile methodology has become increasingly popular in software development in recent years. One of the key components of agile development is estimating the size of user stories, which are small, discrete units of work. There are several methods of estimating the size of user stories, but one of the most commonly used is story points. While story points have their advantages, they also have some drawbacks that can impact the accuracy of estimating. In this article, we'll explore the pros and cons of using story points for agile estimating.
Pros of Using Story Points:
Relative Sizing: One of the primary benefits of using story points is that they allow for relative sizing of user stories. Rather than focusing on the absolute size of a story, the team assigns a number to the story that represents its relative complexity compared to other stories. This approach can help teams avoid the "analysis paralysis" that can occur when trying to assign precise values to stories.
Collaboration: Story points encourage team collaboration during estimation. Because the team members work together to assign points, it can foster a shared understanding of the work to be done. This can help ensure that everyone is on the same page and can lead to more accurate estimates.
Flexibility: Story points are a flexible estimation technique that can adapt to the needs of the team. They can be adjusted as the team gains a better understanding of the work involved, allowing for more accurate estimates over time.
Cons of Using Story Points:
Inconsistency: One of the main drawbacks of story points is inconsistency. Because story points are relative and assigned subjectively, different team members may assign different values to the same story. This can lead to inconsistency and make it difficult to compare estimates across different stories or sprints.
Time-Consuming: Estimating using story points can be time-consuming, particularly for larger projects or teams. The process of assigning points requires careful consideration and collaboration, which can take away from development time.
Lack of Standardization: There is no standardization for assigning story points. While there are some general guidelines, each team may have their own interpretation of what each point value represents. This can lead to confusion and make it difficult to compare estimates across different teams or organizations.
While story points have their advantages, they also have some drawbacks that can impact the accuracy of estimating. The inconsistency and lack of standardization can lead to inaccurate estimates, which can impact project timelines and budgets. However, the relative sizing, collaboration, and flexibility offered by story points can also be valuable tools for estimating. Ultimately, the decision of whether to use story points or another estimation technique will depend on the needs and preferences of the team.
Sources:
Cohn, M. (2006). Agile estimating and planning. Prentice Hall Professional.
Rubinstein, A. (2018). The Pros and Cons of Story Points. Retrieved from https://blog.hellosign.com/the-pros-and-cons-of-story-points/
Grenning, J. (2016). Why the confusion around story points? Retrieved from https://www.agilealliance.org/why-the-confusion-around-story-points/