Planned sprint ADS Q2 W20 - 18-22 May • planning snapshot + end-of-sprint outcome snapshot
This version uses the planning snapshot as the promise set and the outcome snapshot as the result set. Count metrics link to snapshot-exact JQL result pages. Jira IDs in the report link to live Jira issues.
Download DOCXYellow. The sprint closed 6/17 visible items. The team absorbed noise well — all 2 added items were closed — but finish predictability was only 23.1% (3/13), and bugs made up 0.0% of completed items. Planning-baseline carryover includes 10 finish misses and 1 expected progress continuations.
| Metric | Value | How to read it |
|---|---|---|
| Committed completion | 26.7% (4/15) | Planned items marked Done ÷ all planned committed items |
| Planning-baseline carryover | 73.3% (11/15) | All planned items not Done, including expected Progress continuations |
| Finish-intent carryover | 76.9% (10/13) | Finish-intent planned items not Done ÷ all finish-intent planned items |
| Finish predictability | 23.1% (3/13) | Finish-intent planned items done ÷ all finish-intent planned items |
| Progress predictability | 50.0% (1/2) | Progress items that behaved as intended by carrying |
| Added-during-sprint load | 11.8% (2/17) | Outcome-only items ÷ all visible items |
| Added work closure | 2/2 | All added items marked Done |
| Reactive load (bug share) | 0.0% (0/6) | Completed bugs ÷ all completed work |
| Planning quality | 53.3% (8/15) | Committed items marked Ready ÷ all committed items |
| Workflow-truth mismatches | 0 | Items marked Done in review while workflow status remained non-final |
The sprint did not fail; it traded predictability for responsiveness. All 2 added items were closed, but that responsiveness came with 0.0% bug share and diluted finish predictability.
The miss pattern is concentrated: 5 partial-completion carryovers, 1 dependency-driven misses, and 4 planning-baseline items that never really started.
Most misses were not caused by poor readiness. 6 of the 11 planning-baseline carryovers had been marked Ready, so the stronger hypothesis is breakdown, sequencing, and capacity protection rather than simple scoping immaturity.
| Type | Planned | Added | Stretch | Unclear | Total done | Done % |
|---|---|---|---|---|---|---|
| Story | 2 | 2 | 0 | 0 | 4 | 66.7% |
| Task | 1 | 0 | 0 | 0 | 1 | 16.7% |
| Bug | 0 | 0 | 0 | 0 | 0 | 0.0% |
| Signal | Value | Why it matters |
|---|---|---|
| Planning-baseline items | 15 | Items present in the frozen planning snapshot |
| Planning-baseline done | 4 | Closed by sprint review |
| Planning-baseline carryover | 11 | All planned items still open, including Progress continuation |
| Finish-intent carryover | 10 | Planned-to-finish items that did not finish |
| Progress continuation | 1 | Progress-intent planned items still open as expected |
| Planning-baseline items marked Ready | 8 | Planning-quality input |
| Carryovers marked Ready | 6 | Ready did not guarantee closure |
| Carryovers not started | 4 | Execution focus gap |
| Carryovers started but unfinished | 5 | Work moved, but did not close |
| Pattern | Count | What it suggests |
|---|---|---|
| Partial completion | 5 | Breakdown / sizing / stage-gating was not tight enough |
| Dependency delay | 1 | Capacity protection or dependency timing created slip |
| Not started | 4 | A committed item remained outside execution focus |
| In Progress / Code Review carryovers | 5 | Most misses were moving, but not closing |
Items marked Done in the sprint-review field while Jira workflow status was still non-final.
| Jira item | Status | Intent |
|---|---|---|
| None |
| Question | Why this matters | What evidence to ask for |
|---|---|---|
| Why did finish-intent items carry over despite planning readiness? | This tests execution quality rather than just scope quality. | Show finish-intent carryovers split by dependency, partial completion, and not-started. |
| Are Progress items being managed intentionally? | Progress items are allowed to continue, but the continuation should be visible and controlled. | Show the original slice and the specific landing expectation for each item. |
| Is added work a healthy responsiveness level or chronic interruption? | High responsiveness can hide systemic instability and diluted predictability. | Show which added items were urgent/reactive versus discretionary scope change. |
| Can we trust Done in review when workflow is still non-final? | Workflow-truth gaps reduce trust and make completion easy to game. | Show the exact mismatches and the completion rule to enforce next sprint. |
Usage note: start with the top-line metrics, then use the traceability links to answer these questions with issue-level evidence.
| Snapshot / movement | Issue count | Calculation | Link |
|---|---|---|---|
| Planning snapshot raw list | 16 | Frozen planning export before metric exclusions | Open JQL |
| Sprint review / outcome snapshot raw list | 18 | Frozen review export before metric exclusions | Open JQL |
| Normalized sprint fact base | 17 | Deduplicated union used by metrics after canceled/cancelled exclusions | Open JQL |
| Metric planning baseline | 15 | Non-canceled issue keys present in the frozen planning snapshot | Open JQL |
| Metric outcome snapshot | 17 | Non-canceled issue keys present in the frozen sprint-review snapshot | Open JQL |
| Planned and still present at review | 15 | planning_snapshot_present = true and outcome_snapshot_present = true | Open JQL |
| Added after planning | 2 | planning_snapshot_present = false and outcome_snapshot_present = true | Open JQL |
| Planned but missing from review | 0 | planning_snapshot_present = true and outcome_snapshot_present = false | Open JQL |
| Metric-excluded canceled/cancelled rows | 1 | Rows preserved in audit but excluded from every numerator and denominator | Open JQL |
Planning and outcome are separate frozen moments. Raw snapshot counts can be larger than metric counts because canceled/cancelled rows stay in audit but leave all metric denominators.
Added after planning is snapshot-based: present in the outcome snapshot and absent from the planning snapshot. Planned but missing from review shows items that left the sprint snapshot before review.
| Metric | Value | Formula | Numerator / denominator | Denominator evidence |
|---|---|---|---|---|
| Committed completion | 26.7% (4/15) | planned committed items marked Done ÷ all planned committed items | 4/15 | Open denominator JQL |
| Planning-baseline carryover | 73.3% (11/15) | planned baseline items not Done at review ÷ all planned baseline items | 11/15 | Open denominator JQL |
| Finish-intent carryover | 76.9% (10/13) | finish-intent planned items not Done at review ÷ all finish-intent planned items | 10/13 | Open denominator JQL |
| Finish predictability | 23.1% (3/13) | finish-intent committed items marked Done ÷ all finish-intent committed items | 3/13 | Open denominator JQL |
| Progress predictability | 50.0% (1/2) | progress-intent items that carried as intended ÷ all progress-intent committed items | 1/2 | Open denominator JQL |
| Added-during-sprint load | 11.8% (2/17) | visible items absent from planning and present in review ÷ all visible sprint items | 2/17 | Open denominator JQL |
| Added work closure | 2/2 | added visible items marked Done ÷ all added visible items | 2/2 | Open denominator JQL |
| Planning quality | 53.3% (8/15) | committed items marked Ready in planning snapshot ÷ all committed items | 8/15 | Open denominator JQL |
| Carryovers marked Ready | 54.5% (6/11) | carryovers that were marked Ready in planning snapshot ÷ all carryovers | 6/11 | Open denominator JQL |
| Reactive load | 0.0% (0/6) | completed bugs ÷ all completed work | 0/6 | Open denominator JQL |
| Workflow-truth mismatches | 0 | Done rows with non-final workflow status | 0/6 | Open denominator JQL |
Planning-baseline carryover includes both finish-intent misses and expected Progress continuations. Use Finish-intent carryover when you want only planned-to-finish items that did not finish.
| Artifact | Link |
|---|---|
| Issue audit register | Open issue-level audit CSV |
| Metric lineage | Open metric lineage CSV |
| JQL traceability register | Open JQL traceability CSV |
| Sprint metrics JSON | Open sprint metrics JSON |
These companion artifacts keep the pulse debuggable when a leader wants the exact rows behind a metric or a count.