Planned sprint ADS Q2 W20 - 18-22 May • 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 24 of 53 visible items, including 4 Stories, 5 Tasks, and 14 Bugs. Product movement was real, but the sprint was still noisy: 38 items entered after planning and 15 of them were closed. The main misses were concentrated in 29 carryovers.
| Metric | Value | How to read it |
|---|---|---|
| Visible sprint items | 53 | Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses |
| Delivered items | 24 | Items whose final outcome bucket is Done |
| Carry overs | 29 | Items not closed at sprint review |
| Delivered mix | 4 / 5 / 14 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 15 / 38 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 18 / 35 / 0 | 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 |
| Type | Planned | Added | Stretch | Unclear | Total done | Done % |
|---|---|---|---|---|---|---|
| Story | 4 | 0 | 0 | 0 | 4 | 16.7% |
| Task | 4 | 1 | 0 | 0 | 5 | 20.8% |
| Bug | 0 | 14 | 0 | 0 | 14 | 58.3% |
Below are the items marked Done in the sprint review snapshot, grouped by work-item type.
| Jira item | How entered |
|---|---|
| ADS-6495 — Service Internal API | Planned |
| ADS-6501 — Input validation errors | Planned |
| ADS-6562 — Remove any mentions of Laravel in production mode | Planned |
| ADS-6750 — Interfata Minister | Planned |
| Metric | Value | How to read it |
|---|---|---|
| Partial completion | 4 | Carryovers blocked by partial completion |
| Dependency / competing work | 1 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 12 | 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.
One Done row (ADS-6495 — Story — Service Internal API) 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-6501 — Story — Input validation errors) 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-6562 — Story — Remove any mentions of Laravel in production mode) 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-6870 — Bug — [FE][BE] - Ștergere note în perioade blocate) 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-7447 — Bug — Account lookup APIs return HTTP 500 on unsupported Unicode auth inputs due to MySQL collation errors) is still flagged as Late start / sequencing in the outcome file. The report respects the outcome as Done and treats the flag as a data-quality anomaly.
One Done row (ADS-7524 — Task — [FE]: Rute noi ale modalelor pentru mobile) 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-7596 — Task — [FR] Setare "tehnic" pentru calcul medie la scolile de Arte) 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 | 36 | 36 issues in the planning snapshot |
| Sprint review / outcome snapshot raw list | 61 | 61 issues in the Friday review snapshot |
| Normalized sprint fact base | 53 | 53 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.