Committed completion
37.3%
9.8 pts down vs prior checkpoint
Aggregated source-backed sprint trend view
Adservio trend points come from persisted source-pair metrics and the published pulse archive. The dashboard is designed to show miss patterns and execution quality, not just output volume.
Adservio now has 12 source-backed checkpoint(s) in the persisted trend store.
These cards bias toward leadership questions: can we trust the promise set, what diluted it, and what actually came out of the sprint system.
Linked table values open the frozen Jira issue set used as the metric numerator. Percentages also show numerator / denominator so the calculation is visible before drilling down.
| Metric | Definition / formula | Direction |
|---|---|---|
| Committed completion | Committed items marked Done / all committed items | Higher is better |
| Committed carryover | Committed carryovers / all committed items | Lower is better |
| Finish predictability | Finish-intent items marked Done / all finish-intent committed items | Higher is better |
| Progress predictability | Progress-intent items that carried as intended / all progress-intent committed items | Higher is better |
| Added load | Items added after planning / all visible sprint items | Lower is usually better |
| Planning quality | Committed items marked Ready / all committed items | Higher is better |
| Carryovers marked Ready | Carryovers marked Ready at planning / all committed carryovers | Diagnostic |
| Bug share | Bugs delivered / all delivered work | Lower is usually better |
| Stories | Delivered items whose Jira issue type is Story | Count |
| Tasks | Delivered items whose Jira issue type is Task | Count |
| Bugs | Delivered items whose Jira issue type is Bug | Count |
| Partial | Committed carryovers classified as partial completion | Lower is better |
| Dependency | Committed carryovers classified as dependency delay | Lower is better |
| Not started | Committed carryovers that never started | Lower is better |
| Workflow mismatch | Done outcomes whose Jira workflow status was still non-final | Lower is better |
| Not-started committed | Committed items that carried without starting | Lower is better |
| Product stories | Delivered Story count, repeated in the execution-truth view | Count |
No published pulse pair was found for W13, W15, W16, W17. Those weeks remain visible as explicit gaps; the dashboard does not infer zeroes or synthesize metrics for them.
Historical checkpoints were reconstructed from their published pulse metric tables; frozen source-pair rows remain authoritative whenever both are available.
Choose a consecutive week window to inspect how the delivery system changed over time for this scope.
| Metric | W11-12 | W13 | W14 | W15 | W16 | W17 | W18 | W19 | W20 | W21 | W22 | W23 | W24 | W25 | W26 | W27 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Stories | 5 | — | 0 | — | — | — | 4 | 6 | 10 | 2 | 7 | 9 | 7 | 8 | 10 | 9 |
| Tasks | 4 | — | 3 | — | — | — | 15 | 4 | 8 | 14 | 10 | 14 | 9 | 9 | 11 | 7 |
| Bugs | 6 | — | 4 | — | — | — | 17 | 7 | 19 | 33 | 22 | 30 | 20 | 27 | 27 | 28 |
| Partial | 2 | — | 2 | — | — | — | 7 | 4 | 12 | 14 | 12 | 6 | 14 | 15 | 9 | 11 |
| Dependency | 1 | — | 1 | — | — | — | 1 | 0 | 3 | 5 | 5 | 3 | 3 | 2 | 4 | 5 |
| Not started | 1 | — | 0 | — | — | — | 11 | 2 | 18 | 17 | 25 | 20 | 22 | 24 | 15 | 25 |
| Workflow mismatch | 2 | — | 0 | — | — | — | 4 | 3 | 5 | 1 | 5 | 6 | 2 | 4 | 18 | 0 |
| Not-started committed | 1 | — | 0 | — | — | — | 11 | 2 | 18 | 17 | 25 | 20 | 22 | 24 | 15 | 25 |
| Product stories | 5 | — | 0 | — | — | — | 4 | 6 | 10 | 2 | 7 | 9 | 7 | 8 | 10 | 9 |