I’ll introduce my personal metrics for converting story points (estimation points) to time in Scrum development.
Background Knowledge
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:
- アジャイル開発とは（中編）スクラムとエクストリームプログラミング（XP） : 富士通ソフトウェアテクノロジーズ
- スクラム (ソフトウェア開発) - Wikipedia
- 📖 SCRUM BOOT CAMP THE BOOK
Story Points
Please read the following articles about story points in Scrum development and the anti-pattern of converting story points to time:
- スクラムでの見積もり(ストーリーポイント) | masaytan's blog
- ストーリーポイントとは何か？必要ものなのか？
- ストーリーポイントに関する15個のよくある質問と答え – Ryuzee.com
- ストーリーポイントで見積もる現実的な方法 - Qiita
- 「ストーリーポイント神話」を考える - bluebird
Practicing the Pomodoro Technique
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.
Time Conversion Metrics for Story Points
Purpose of Converting Story Points to Time
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.
When Using Fibonacci Numbers for Story Points
| 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.