I’ll introduce my personal metrics for converting story points (estimation points) to time in Scrum development.
This article doesn’t cover “What is Scrum development?” It’s written assuming knowledge of Scrum development.
If you’re not familiar with Scrum development, please read the following:
Please read the following articles about story points in Scrum development and the anti-pattern of converting story points to time:
As a personal work technique, I’ve been practicing the Pomodoro Technique since around 2016.
So I convert about 1 Pomodoro (30 minutes) to the minimum unit of 1 story point.
I convert story points to time because I want to have my own metrics when aligning point understanding when joining a new Scrum team.
Therefore, the following story point time conversion table is only used personally and is not shared within the Scrum team.
Estimated Points (見積りポイント) | Time |
---|---|
0 | 0 |
1 | 0.5 ~ 1 hour |
2 | 2 ~ 3 hours |
3 | 1 day |
5 | 2 days |
8 | 3 days |
13 | 1 week |
21 | 2 weeks |
? | Unknown |
I basically try to decompose tasks when they get 8 points or more.
When 13 points or more are assigned, it becomes a high-uncertainty estimate, so I add tasks for effort estimation to the Backlog and re-estimate story points after completing those tasks.
That’s all from the Gemba.