3 ms·
Re: It's the sprint versus marathon mindset. As someone who did track in high school, the whole agile nomenclature around "sprint" continues to rub me the wron
by steveBK123 6y ago
Re: It's the sprint versus marathon mindset.
As someone who did track in high school, the whole agile nomenclature around "sprint" continues to rub me the wrong way. If you aren't a startup facing a launch-or-fail moment, the approach should be much more that of a marathon.
I was joking with my wife that "sprint" to me implies that you go all out and then take a long break before you go again. We should be treating the longterm plan like a marathon and the intermediate steps like "splits".
If you are working on a product that's been around for years , the idea that you are an all-star for delivering your 5 points the day before your 2 weeks sprint ends and a lazy jerk if you deliver it the day after sprint ends just incentivizes a lot of shorterm-ism and corner cutting.
The model of working "all out" and your "break" for planning is a 2 hour meeting in between sprints where you get praised or scorned for a 10% difference in delivery speed is..
- matwood 6y agoSplits works, but I tend to use iteration. There are benefits to breaking work into chunks and checking in how it's going every 2-4 weeks, but there's no reason to be in perpetual crunch time. There should also be free time at the end of every iteration to do some problem/design/idea exploration.