Sprint Gaps: A Weekend for Your Sprint

The first article in this series addressed how to fit sprints to business context, with the analogy that people naturally change their routines when they go on vacation, almost without thinking about it. This second installment will talk about intentionally bringing the breaks people take in personal life into software engineering schedules, in a way that makes teams more productive. In a perfect world, software backlogs would be forever neatly groomed, maintained and prioritized. Features would always be delivered the right way, the first time. Long-term goals would be balanced with short-term goals. There would be no quick hacky fixes, and technical debt would not accumulate. Of course, nobody is perfect. These things don’t happen unless they get prioritized. But what if these things could occur without managers having to explicitly prioritize them? What if they passively became part of the process? ...

August 27, 2019 · 5 min · Alison Rowland