Planned sprint ADS Q2 W22 - 01-05 Iunie • 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 31 of 64 visible items, including 2 Stories, 6 Tasks, and 17 Bugs. Product movement was real, but the sprint was still noisy: 47 items entered after planning and 25 of them were closed. The main misses were concentrated in 33 carryovers.
| Metric | Value | How to read it |
|---|---|---|
| Visible sprint items | 64 | Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses |
| Delivered items | 31 | Items whose final outcome bucket is Done |
| Carry overs | 33 | Items not closed at sprint review |
| Delivered mix | 2 / 6 / 17 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 17 / 47 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 17 / 43 / 0 | 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 |
| Signal | Value | How to read it |
|---|---|---|
| Available capacity | 50 | Policy-weighted engineering availability after holidays and OOO |
| Nominal capacity | 54.4 | Active workdays after weekends and bank holidays, before OOO |
| OOO capacity | 4.4 | Vacation / OOO days from tracker evidence when present |
| Bank holiday capacity | 13.6 | Policy-weighted public-holiday capacity removed from the sprint window |
| Included people | 18 | People with non-zero implementation capacity in this sprint window |
Capacity is companion context for the pulse; it does not alter snapshot issue-count denominators.
It is not a true hours estimate.
OOO tracker export: capacity_ooo_tracker_export.csv
Pavel Petronel replaced Dron Gabriel
Paul Tanasuca ended without configured replacement
Rojan Shrestha replaced Raul Popovici
Below are the items marked Done in the sprint review snapshot, grouped by work-item type.
| Jira item | How entered |
|---|---|
| ADS-6360 — [Catalog PDF] - Număr indicatori incorect – Semestre | Planned |
| ADS-7776 — [MOB / FE] Add post message when user create/delete group | Added |
| Metric | Value | How to read it |
|---|---|---|
| Partial completion | 6 | Carryovers blocked by partial completion |
| Dependency / competing work | 1 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 20 | 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.
One Done row (ADS-6360 — Story — [Catalog PDF] - Număr indicatori incorect – Semestre) is still flagged as Partial completion in the outcome file. The report respects the outcome as Done and treats the flag as a data-quality anomaly.
One Done row (ADS-7533 — Bug — medii_generale.php: secretary final averages page reads missing $cicluSelectatID when cycle filter is empty - 3 warnings/24h) is still flagged as Not started in the outcome file. The report respects the outcome as Done and treats the flag as a data-quality anomaly.
One Done row (ADS-7591 — Bug — Elevi_transfer.php: missing source repartition row breaks subject transfer - 48 warnings/24h) is still flagged as Not started in the outcome file. The report respects the outcome as Done and treats the flag as a data-quality anomaly.
One Done row (ADS-7621 — Task — [BE][Catalog] - Calcul indicator sa fie facut pe BE) is still flagged as Partial completion in the outcome file. The report respects the outcome as Done and treats the flag as a data-quality anomaly.
One Done row (ADS-7718 — Bug — [FE][Clasele Mele] - Modalul de setari tipuri note nu functioneaza corect pe mobile) is still flagged as Not started in the outcome file. The report respects the outcome as Done and treats the flag as a data-quality anomaly.
| 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 | 52 | 52 issues in the planning snapshot |
| Sprint review / outcome snapshot raw list | 66 | 66 issues in the Friday review snapshot |
| Normalized sprint fact base | 64 | 64 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.