4 ms·
Sprints need not be anything more than “what did you get done this week?” It’s useful to feel progress. It’s useful to notice when things turn out to be more co
by closeparen 3y ago
Sprints need not be anything more than “what did you get done this week?” It’s useful to feel progress. It’s useful to notice when things turn out to be more complex than we thought (dragging the same task from sprint to sprint). It’s useful to notice when unplanned work crowds out planned work.
I don’t think it’s useful to have a very rigorous planning process, or be persnickety about things finishing within the sprint vs. 2-3 days carryover. I particularly hate the rituals designed to reduce autonomy, like PMs managing backlog priority or story points poker exercises. On my team engineers are responsible for their projects and the sprints are just periodic check-ins where you say what you have been doing and what’s next.