Planned sprint ADS Q2 W21 - 25-29 Mai • 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 37 of 75 visible items, including 0 Stories, 8 Tasks, and 26 Bugs. Product movement was real, but the sprint was still noisy: 61 items entered after planning and 35 of them were closed. The main misses were concentrated in 38 carryovers.
| Metric | Value | How to read it |
|---|---|---|
| Visible sprint items | 75 | Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses |
| Delivered items | 37 | Items whose final outcome bucket is Done |
| Carry overs | 38 | Items not closed at sprint review |
| Delivered mix | 0 / 8 / 26 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 14 / 61 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 19 / 53 / 0 | Ready / At risk / Not Ready across the normalized sprint fact base |
| Progress items behaving as intended | 3/5 | 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 | 1 | 7 | 0 | 0 | 8 | 21.6% |
| Bug | 0 | 26 | 0 | 0 | 26 | 70.3% |
Below are the items marked Done in the sprint review snapshot, grouped by work-item type.
| Jira item | How entered |
|---|
| 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 | 15 | 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-6464 — Bug — [Editeaza elev] - a disparut rolul de Elev/Părinte) 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-6974 — Bug — [Catalog Pdf] - Management clasa - Documente - Catalogul clasei) 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-7262 — Task — [Coordonator][Catalog][Absente][Note] - Updates) 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-7460 — Bug — Absences time interval export_xls returns HTTP 500 for inverted date range (6 errors/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-7614 — Bug — [FE] - Eroare 403 la autentificare in cont profesor in browser) 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-7619 — Bug — [FE] - Directorul este deconectat din browser si redirectionat la autentificare la accesarea modulului Documente) 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-7645 — Bug — Certificates API fails when cerReason exceeds cat_certificate_reasons column length - 14 errors/24h) 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.
| 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 | 84 | 84 issues in the Friday review snapshot |
| Normalized sprint fact base | 75 | 75 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.