Planned sprint ADS Q2 W19 - 11-15 May • planning snapshot + end-of-sprint outcome snapshot
This retrospective uses the planning snapshot as the baseline promise set for sprint intent and entry kind, and the outcome snapshot as the actual end-of-sprint result.
Download DOCXYellow. The sprint closed 1 of 56 visible items, including 0 Stories, 0 Tasks, and 0 Bugs. Product movement was real, but the sprint was still noisy: 42 items entered after planning and 0 of them were closed. The main misses were concentrated in 55 carryovers.
| Metric | Value | How to read it |
|---|---|---|
| Visible sprint items | 56 | Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses |
| Delivered items | 1 | Items whose final outcome bucket is Done |
| Carry overs | 55 | Items not closed at sprint review |
| Delivered mix | 0 / 0 / 0 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 14 / 42 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 15 / 39 / 0 | Ready / At risk / Not Ready across the normalized sprint fact base |
| Progress items behaving as intended | 5/6 | Progress items were expected not to finish in this sprint |
| Type | Planned | Added | Stretch | Unclear | Total done | Done % |
|---|---|---|---|---|---|---|
| Story | 0 | 0 | 0 | 0 | 0 | 0.0% |
| Task | 0 | 0 | 0 | 0 | 0 | 0.0% |
| Bug | 0 | 0 | 0 | 0 | 0 | 0.0% |
Below are the items marked Done in the sprint review snapshot, grouped by work-item type.
| Jira item | How entered |
|---|
| Jira item | How entered |
|---|
| Jira item | How entered |
|---|
| Metric | Value | How to read it |
|---|---|---|
| Partial completion | 0 | Carryovers blocked by partial completion |
| Dependency / competing work | 0 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 0 | Committed item never really got underway |
This product pulse is retrospective only and uses the planning snapshot for baseline fields and the outcome snapshot for actuals.
5 rows have Sprint Intent = Progress and remained open; they are treated as healthy continuation rather than finish misses.
| Report element | How to drill down | Traceability mechanism |
|---|---|---|
| Delivered Stories / Tasks / Bugs | Click the section count rows | Snapshot-exact JQL by issuekey list |
| Carry overs / not delivered | Click the Carry overs count | Snapshot-exact JQL by issuekey list |
| Miss pattern summary | Click each miss-pattern count | Snapshot-exact JQL by issuekey list |
| Snapshot | Issue count | Link |
|---|---|---|
| Planning snapshot raw list | 24 | 24 issues in the planning snapshot |
| Sprint review / outcome snapshot raw list | 60 | 60 issues in the Friday review snapshot |
| Normalized sprint fact base | 56 | 56 issues used for metrics and drill-down |
Planning and outcome are separate frozen moments.
Metric tables use the normalized sprint fact base, which keeps planning-only misses and outcome-only additions visible for traceability.
| 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 |
Use these files when you need to validate the exact rows and formulas behind a pulse claim.