Planned sprint ADS Q3 W34 - 24-28 Aug • 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 14 of 30 visible items, including 2 Stories, 1 Tasks, and 9 Bugs. Product movement was real, but the sprint was still noisy: 12 items entered after planning and 6 of them were closed. The main misses were concentrated in 16 carryovers.
| Metric | Value | How to read it |
|---|---|---|
| Visible sprint items | 30 | Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses |
| Delivered items | 14 | Items whose final outcome bucket is Done |
| Carry overs | 16 | Items not closed at sprint review |
| Delivered mix | 2 / 1 / 9 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 18 / 12 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 11 / 16 / 3 | Ready / At risk / Not Ready across the normalized sprint fact base |
| Progress items behaving as intended | 2/2 | Progress items were expected not to finish in this sprint |
Below are the items marked Done in the sprint review snapshot, grouped by work-item type.
| Jira item | How entered |
|---|---|
| ADS-7111 — Conturi parinti active/inactive | Planned |
| ADS-8105 — Impartirea pe module | Added |
| Jira item | How entered |
|---|---|
| ADS-8516 — Routes calendar details | Planned |
| Metric | Value | How to read it |
|---|---|---|
| Partial completion | 3 | Carryovers blocked by partial completion |
| Dependency / competing work | 1 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 4 | 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.
2 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 | 26 | 26 issues in the planning snapshot |
| Sprint review / outcome snapshot raw list | 38 | 38 issues in the Friday review snapshot |
| Normalized sprint fact base | 30 | 30 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.