Barış Erkent // Agile Coach - Allianz Türkiye
User story scoring may seem complicated at first, especially for teams that have just switched to agility. Let's make the story points a little more understandable for beginners.
As you know, user story scoring is a technique that helps predict the complexity and development time of stories. The story points are directly related to the effort shown in while carrying them out. They help team members working at different speeds communicate and estimate the amount of work they will do while working together. Whether you are making predictions with cards, body measurements or Fibonacci number series, what you should keep in mind is that story points are relative units of measurement.
A senior team member can complete a specific job list (backlog) item in 8 hours, while a newer and inexperienced member can take 16 hours to do the same job. But both should make predictions with a common understanding, agreeing that this is a 1-point story.
Now, let's examine the reason why 1 point does not equal a certain number of hours.
In the simplest form, let's imagine that there are two members on the team: one is experienced, the other is new. A task that a new member can complete in four hours can be completed in one hour by an experienced member. In a team's work list of 25 points as follows, the experienced member can complete the sprint with four times more points, since he is four times more productive. In other words, 20 of the planned 25 points in the sprint are made by the senior member and 5 by the new member. The new member can work on any of the five items and successfully complete it during the sprint. Let's say he chose item D. In this case, items A, B and C are left to the senior member.
So, what do we say to someone who asks “How many hours does it take to complete 1 point?” Assuming that 1 week is a 40-hour sprint for this example, there are three possible answers:
- The senior member works 40 hours and gives 20 points. Therefore, 1 point = 2 hours of work.
- The new member works for 40 hours and gives 5 points. Therefore, 1 point is = 8 hours. This corresponds to the first assumption that the senior member is 4 times more productive.
- They work together for 80 hours and complete 25 points. Therefore, 1 point = 3.2 hours (80/25).
We can also understand from this example that there is no equivalence between the score and the time. For the senior member 1 point is 2 hours, while it is 8 hours for the new member and 3.2 hours for the team. However, if the team defines 1 point as 3.2 hours, both of them cannot agree on estimates because they give very different results in 3.2 hours. Yes, story points are related to effort, but the time it takes to complete each point cannot be fixed to the same amount for all team members.
The other problem with equalizing scores to specific hours is that team members no longer think abstractly. When you try to convert story points to hours, you start a calculator in each team member's head that rotates from clock to story points. Team members will first make a mental prediction using the number of hours, and then translate this prediction into points.
In summary, although it is mathematically possible for members who can complete a story in different hours to fixate on finishing it in the same time; they move away from each other when agreeing on a prediction. When the relationship between points and hours becomes equivalent, the points no longer become relative, and the prediction becomes completely dependent on who is doing the work. This situation is both addictive and unsustainable. Especially during member changes in teams, in examples where members with high expertise in certain jobs leave or transfer jobs with new members, these dependencies force teams and prevent their agile work. And none of us, on any team, want to go through this, right?
P.S. You can contact us by clicking here to share your experiences and ask questions about the agile working method.
Reference: https://www.mountaingoatsoftware.com/blog/dont-equate-story-points-to-hours
Comments