3 ms·
Only today I was thinking how agile "sprints" are the wrong terminology. No one wins a marathon by running back-to-back sprints. I know it's only terminology bu
by hopeless 15y ago
Only today I was thinking how agile "sprints" are the wrong terminology. No one wins a marathon by running back-to-back sprints. I know it's only terminology but I think it affects our approach and in practice can encourage a Continuous Death March instead of the intended manageable workload.
- _dps 15y agoI wonder whether there's some hidden wisdom in the terminology. Agile "sprints" are (in the folk-wisdom) ideal for getting somewhere quickly precisely when you don't know where you want to finish. In this case a "quick sprint, rest, reorient, sprint again" metaphor seems appropriate. On the other hand, long-running maintenance work with a stable goal over a year or more probably benefits much less from sprinting. I guess in this case we would need to know what "marathon" development would be :-)
- eliot_sykes 15y agoI'm in favour of using iteration over sprint