Our sprint goal changes every few days. How should we respond?
Unstable sprint purposeProtect a meaningful short-term goal while discussing new information with the Product Owner. Negotiate work without quietly replacing the goal whenever another request appears.
What to do now
- Clarify the current goal
- Assess the new request's urgency and relevance
- Discuss scope options with the Product Owner
- Make any necessary framework-level decision explicitly
When to escalate
Escalate when
The goal has become obsolete or essential work cannot wait.
Who decides
The relevant Scrum accountability or delivery owner
Example
A team defers an unrelated enhancement while adapting details needed to achieve the current goal.
Mistake to avoid
Treating every stakeholder request as an automatic sprint commitment.
Prevent a repeat
Inspect useful outcomes and feedback; apply Scrum-specific rules only when the team is actually using Scrum.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Resources
Represent agreed work and evidence with enabled task features; do not imply native Scrum automation or certified Scrum compliance. See the platform
Related cases
- We carry unfinished work into every sprint. What should we inspect?Persistent delivery overcommitment
- We have no clear product goal. What should guide the backlog?Directionless backlog ordering
- The client changes their mind repeatedly. How do we manage the relationship?Repeated preference changes
- How do we plan a portfolio when strategy changes frequently?Unstable strategic demand