Renegotiate Scope Without Losing the Goal
Handle new scope by protecting the Sprint Goal and making schedule tradeoffs explicit.
Adaptation is a tradeoff conversation. Protect the Sprint Goal first A new request is not automatically bad. It becomes dangerous when the team accepts it without checking whether it endangers the Sprint Goal. Check path impact before saying yes Critical-path work has little or no schedule float. Pulling capacity from it changes the project, even if the board still looks active. Update RAID immediately New scope often creates fresh assumptions and dependencies. Record them while the decision is being made, not after the risk has matured into an issue.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in