Battlecard: We Do Not Have Time For Retros
Respond credibly when someone argues that retros should be skipped because delivery pressure is high.
We do not have time for a retro right now. We need to get back to delivery. That pressure is exactly why we need a tight retro. The point is not ceremony. It is choosing one change that makes the next sprint less likely to burn us the same way. The response validates the pressure, then reframes the retro as the team’s improvement loop instead of optional reflection time. It keeps the ritual tied to quality and effectiveness, which is the principle the Scrum Guide names. A rough sprint, incident, or release where the team is tempted to skip reflection…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in