Make the sprint goal the trade-off filter
Use a Sprint Goal to decide what belongs in a sprint and what should wait.
The move: use the Sprint Goal as the sentence that decides what changes when pressure arrives. A good Sprint Goal names the outcome the team is trying to create, not the inventory of tickets it hopes to finish. That matters because agile teams are constantly hit with new information: support escalations, stakeholder requests, technical surprises, and discovery from the work itself. If the sprint is only a list, every new request becomes a negotiation against every person. If the sprint has a goal, the negotiation is against the outcome. The goal also protects collaboration. Developers can adjust implementation details, split…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in