Re:Go Slow to Go Fast
by hopeless on Friday December 30, 2011 @07:15PM
(#3409639)
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.
[ Parent
| on HN ]
I 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 :-)
Re:Go Slow to Go Fast
by eliot_sykes on Sunday January 01, 2012 @05:29AM
(#3412830)
I'm in favour of using iteration over sprint