diff options
| author | alex <alex@pdp7.net> | 2026-04-30 20:39:57 +0200 |
|---|---|---|
| committer | alexpdp7 <alex@corcoles.net> | 2026-05-04 07:57:33 +0000 |
| commit | 9aab9437a0ef59390439f2ce52698f760ea8356f (patch) | |
| tree | ec3b6ff4d4826b4c859ba1b1c89ac9b70710caad /blog/content/notes/tech | |
| parent | de747ccd88f88f095d2ad9af6dcbeee9ff863906 (diff) | |
Talk less about stakeholders and story points.master
Diffstat (limited to 'blog/content/notes/tech')
| -rw-r--r-- | blog/content/notes/tech/on-software-development.gmi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/blog/content/notes/tech/on-software-development.gmi b/blog/content/notes/tech/on-software-development.gmi index e22041d8..5c549f9e 100644 --- a/blog/content/notes/tech/on-software-development.gmi +++ b/blog/content/notes/tech/on-software-development.gmi @@ -56,7 +56,7 @@ 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. -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.) +Story points are not useful for stakeholders because story points are nearly completely unrelated to value. 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. |