Timeline for Fibonacci scale project estimates: how is it not vulnerable to misunderstanding by management?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30, 2019 at 11:51 | answer | added | Barnaby Golden | timeline score: 3 | |
| Aug 30, 2019 at 7:41 | comment | added | Bart van Ingen Schenau | "Considering the whole point of the Fibonacci scale is to provide some sense of exponential effort between tasks" That is not the point of the Fibonacci scale, because that can also be seen in continuous-scale hour estimations. The point of the Fibonacci scale is in the increasing gaps between the numbers: As work packages grow larger, their estimates become less accurate. A 13-point story is estimated to take between 8 and 20 times as much effort as a 1-point story, as there are no other values within that range. | |
| Aug 30, 2019 at 0:46 | comment | added | Todd A. Jacobs♦ | Correct. Treating it as a performance metric is a known anti-pattern. Its actual purpose is primarily to help the team avoid over-committing during Sprint Planning, and as an early-warning system to draw attention to hidden blockers. | |
| Aug 29, 2019 at 23:38 | comment | added | 8protons | @ToddA.Jacobs So it's not supposed to be a way for management to hold a team accountable for their efficiency? | |
| Aug 29, 2019 at 23:30 | comment | added | Todd A. Jacobs♦ | Developers don’t have velocity. Teams do, and it’s supposed to be a planning tool rather than a productivity metric. Using it to measure individual performance is Doing Story Points and Agile Leadership Wrong™. | |
| Aug 29, 2019 at 22:55 | answer | added | dyson | timeline score: 1 | |
| Aug 29, 2019 at 18:20 | review | First posts | |||
| Aug 29, 2019 at 19:24 | |||||
| Aug 29, 2019 at 18:18 | history | asked | 8protons | CC BY-SA 4.0 |