3 ms·
The problem is that Scrum "sprints" are like treating a marathon as 422 contiguous 100m dashes. Yep. Or to put it another way, too many shops seem to think th
by mindcrime 11y ago
The problem is that Scrum "sprints" are like treating a marathon as 422 contiguous 100m dashes.
Yep. Or to put it another way, too many shops seem to think that you can "sprint" ALL THE TIME. And while it's "only a metaphor", it's a meaningful one in this case. You can't:
sprint -> sprint -> sprint -> sprint -> sprint -> sprint -> ∞
You have to:
sprint -> sprint -> breather -> sprint -> breather -> sprint -> sprint -> breather -> ∞
or something like that.
- UK-AL 11y agoSprints aren't sprints. Replace sprint with time segment. And you get more accurate picture.
- mindcrime 11y agoSprints aren't sprints. Except when they are. And just using that term encourages people to treat them like actual sprints, instead of just metaphorical sprints. This is why I advocate for use of the term "iteration" instead. But even then, I think it's important to include "slack" iterations that are for random bug fixes, miscellaneous refactoring, etc., that is developer driven, not business user driven.