Planned sprint ADS Q3 W27 - 06-10 Jul • 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 9 of 20 visible items, including 2 Stories, 1 Tasks, and 4 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 11 carryovers.
| Metric | Value | How to read it |
|---|---|---|
| Visible sprint items | 20 | Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses |
| Delivered items | 9 | Items whose final outcome bucket is Done |
| Carry overs | 11 | Items not closed at sprint review |
| Delivered mix | 2 / 1 / 4 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 8 / 12 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 6 / 13 / 1 | Ready / At risk / Not Ready across the normalized sprint fact base |
| Progress items behaving as intended | 3/3 | 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-6980 — Tracing & Error Logging | Planned |
| ADS-8072 — Admitere - Structură proiect, documentație, teste automate back-end | Planned |
| Jira item | How entered |
|---|---|
| ADS-7319 — [Preferinte][Admin] - Stiri | Added |
| Jira item | Why it carried |
|---|---|
| ADS-4007 — Bug — [BE][Subscriptions] - Comportament ciudat featureflags in cazul in care sunt dezactivate subscriptiile | Not started |
| ADS-4328 — Story — Headers in Mobile App | Not started |
| ADS-6159 — Story — Notification Center for Mobile | Partial completion |
| ADS-6201 — Story — Log formatting - node.js, subscriptions | Not started |
| ADS-6675 — Story — [Financiar] - Managementul penalitatilor | Partial completion |
| ADS-7343 — Task — [Stiri] - Distribuie Updates | Partial completion |
| ADS-7474 — Task — [FE] - Optimizare viteză de încărcare pagini | Partial completion |
| ADS-7849 — Story — Stergere date S3 | Partial completion |
| ADS-8071 — Story — Teste automate flow Subscripții | Partial completion |
| ADS-8211 — Bug — [Admitere] - In pagina de 'Editeaza documente' apar datele altui candidat | Partial completion |
| ADS-8215 — Bug — [Admitere] [UPA]- In exporturi nu apar datele personale ale candidatului | Not started |
| Metric | Value | How to read it |
|---|---|---|
| Partial completion | 5 | Carryovers blocked by partial completion |
| Dependency / competing work | 0 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 2 | 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.
3 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 | 15 | 15 issues in the planning snapshot |
| Sprint review / outcome snapshot raw list | 24 | 24 issues in the Friday review snapshot |
| Normalized sprint fact base | 20 | 20 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.