The team estimates stories before understanding them. What should happen?
Premature backlog estimationClarify purpose, boundaries, examples, and major uncertainties before treating an estimate as useful. Use a short learning activity when uncertainty dominates the work.
What to do now
- Discuss the intended user outcome
- Identify missing examples and constraints
- Split or investigate uncertain work
- Estimate with explicit assumptions
When to escalate
Escalate when
A commitment depends on unresolved feasibility questions.
Who decides
The relevant Scrum accountability or delivery owner
Example
A story receives a discovery task before the team estimates an unfamiliar external integration.
Mistake to avoid
Forcing a point value to make the planning spreadsheet complete.
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
- Our work items are too large to finish in an iteration. How should we split them?Oversized delivery batches
- The team counts partially finished stories as done. How should we report them?Incomplete work misclassified
- How do we estimate work we have never done before?High-uncertainty estimation
- Who should perform user acceptance testing?Unclear business verification ownership