How do we show agile progress to executives without misleading percentages?
Outcome-focused adaptive reportingReport usable outcomes, current goals, forecast ranges, major constraints, and decisions. Avoid converting an evolving backlog into a false percentage of a fixed total.
What to do now
- Identify the executive decision needs
- Show completed usable outcomes
- Explain remaining uncertainty and forecasts
- Highlight choices needed to protect value
When to escalate
Escalate when
A fixed external commitment is threatened by current evidence.
Who decides
The relevant Scrum accountability or delivery owner
Example
An executive update shows validated workflows and the remaining release-critical capabilities.
Mistake to avoid
Calculating completion from a backlog whose denominator changes every week.
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
- The team has too much unplanned work for stable iterations. What can we do?Delivery model-demand mismatch
- Should defects always go into the next sprint?Context-free defect prioritization
- Should executives see every project issue?Unfiltered executive reporting
- Different reports show different completion percentages. Which one is right?Inconsistent progress definitions