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 2 of 9 visible items, including 0 Stories, 0 Tasks, and 1 Bugs. Product movement was real, but the sprint was still noisy: 0 items entered after planning and all of them were closed. The main misses were concentrated in 7 carryovers.
| Metric | Value | How to read it |
|---|---|---|
| Visible sprint items | 9 | Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses |
| Delivered items | 2 | Items whose final outcome bucket is Done |
| Carry overs | 7 | Items not closed at sprint review |
| Delivered mix | 0 / 0 / 1 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 9 / 0 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 5 / 3 / 1 | 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 |
|---|
| Jira item | How entered |
|---|
| Jira item | How entered |
|---|---|
| ADS-5808 — [MOB][Wellbeing] - Parintele nu poate vizualiza testele de autocunoastere pe mob | Planned |
| Jira item | Why it carried |
|---|---|
| ADS-4419 — Story — [Elev][Părinte] - Redesign - Noutati & Activitati | Partial completion |
| ADS-8297 — Story — [Elev][Parinte] - Redesign - Materii | Partial completion |
| ADS-8298 — Story — [Elev][Parinte] - Redesign - Gradinite | Not started |
| ADS-8378 — Story — [Elev][Parinte] Materie detalii | Partial completion |
| ADS-8533 — Task — Logout methods helper | Partial completion |
| ADS-8541 — Bug — Class management day diary | Partial completion |
| ADS-8558 — Story — [Elev][Părinte] - Materii - Observații si conduita | Partial completion |
| Metric | Value | How to read it |
|---|---|---|
| Partial completion | 6 | Carryovers blocked by partial completion |
| Dependency / competing work | 0 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 1 | 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 | 9 | 9 issues in the planning snapshot |
| Sprint review / outcome snapshot raw list | 9 | 9 issues in the Friday review snapshot |
| Normalized sprint fact base | 9 | 9 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.