diff options
| author | alex <alex@pdp7.net> | 2026-04-30 17:18:30 +0000 |
|---|---|---|
| committer | alexpdp7 <alex@corcoles.net> | 2026-05-04 07:57:33 +0000 |
| commit | de747ccd88f88f095d2ad9af6dcbeee9ff863906 (patch) | |
| tree | 927c25dd3630c48661385aa0a0db3019de2fc5f3 /blog/content/notes/tech | |
| parent | ac5f2cb7a5803f5cb29f7545c87361e7d91e2658 (diff) | |
Clarify lack of utility of story points to stakeholders
Expand a bit on problems of velocity as story points per sprint.
Diffstat (limited to 'blog/content/notes/tech')
| -rw-r--r-- | blog/content/notes/tech/on-software-development.gmi | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/blog/content/notes/tech/on-software-development.gmi b/blog/content/notes/tech/on-software-development.gmi index 07743124..e22041d8 100644 --- a/blog/content/notes/tech/on-software-development.gmi +++ b/blog/content/notes/tech/on-software-development.gmi @@ -56,7 +56,9 @@ Story points can be useful if planning poker helps developers address misunderst Story points are most useful the more detached from time they are. Associating story points with time puts useless pressure on developers that reduces their usefulness. -In my experience, the number of value-delivering stories done per sprint is a good enough measure of progress. The amount of story points delivered per sprint does not have any value to stakeholders because story points are completely unrelated to value. +Story points are not useful for stakeholders because story points are nearly completely unrelated to value. (If anything, stakeholders should favor stories with smaller estimations.) + +In my experience, the number of value-delivering stories done per sprint is a good enough measure of progress. Analyzing the total number of story points does not add much value in most cases, and might bias developers in their estimations and their prioritization without reason. ## Further reading |