3 ms·
Does it bother anyone else that we use the word "sprint" in agile? Does it make sense to always be "sprinting"? Personally, the idea of floating down a waterfa
by asow92 3y ago
Does it bother anyone else that we use the word "sprint" in agile? Does it make sense to always be "sprinting"?
Personally, the idea of floating down a waterfall sounds way more appealing.
- mindcrime 3y agoDoes it bother anyone else that we use the word "sprint" in agile? FWIW, that's not a universal thing. A lot of people use "iteration" in preference to "sprint" - but sadly, not enough. I think the term "sprint" should be abolished personally. Does it make sense to always be "sprinting"? Absolutely not. And it may be "just a metaphor" but I think the metaphors we use matter. And you absolutely can't be "always sprinting". It's an absurd notion.
- topaz0 3y agoMaybe the next methodology should be "lazy river" or similar.
- broast 3y agoThe part where you are floating is not the waterfall
- asow92 3y agoTouché, but can we call standup the splash zone?
- crazygringo 3y agoIt's meant to be a metaphor only for distance, not for speed. In running/swimming, the short events are called sprints. In contrast with long-distance events. Does anybody have a better metaphor, a noun word that suggests a short distance, in contrast against a long distance? (E.g. "block" or "jump" or "hop" don't really work because none of them inherently communicate the idea of shorter -- a hop is longer than a step, for instance.)
- rawgabbit 3y agoInterval?
- crabmusket 3y agoWe used to use "sprint" by default. We started using Linear, and they call them "cycles", which prompted me to reconsider and now we've adopted that.