Planned sprint ADS Q2 W23 - 08-12 June • 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 66 visible items, including 2 Stories, 11 Tasks, and 20 Bugs. Product movement was real, but the sprint was still noisy: 33 items entered after planning and 25 of them were closed. The main misses were concentrated in 29 carryovers.
| Metric | Value | How to read it |
|---|---|---|
| Visible sprint items | 66 | 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 | 29 | Items not closed at sprint review |
| Delivered mix | 2 / 11 / 20 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 33 / 33 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 27 / 39 / 0 | Ready / At risk / Not Ready across the normalized sprint fact base |
| Progress items behaving as intended | 0/1 | 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-6360 — [Catalog PDF] - Număr indicatori incorect – Semestre | Planned |
| ADS-7813 — [FE] Student details modal overflow | Planned |
| Metric | Value | How to read it |
|---|---|---|
| Partial completion | 2 | Carryovers blocked by partial completion |
| Dependency / competing work | 0 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 19 | 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.
0 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-7009 — Task — Dezactivare actiuni noteaza(si bulk) daca media anuala si/sau media semestriala este incheiata) 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-7062 — Improvement — [FE] - Calcul si afisare total pentru elevi inscrisi pe varste) 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-7451 — Bug — [BE] - Condica - Activitati duplicate) 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-760 — Bug — [Classes][LCY][WEB][FE/MOB] - Classroom - Unable to delete a document attached to a message) 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-7662 — Improvement — [FE]: Laravel Schimabri pe FE - boilerplate) 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-7724 — Task — [FR] Setare calcul medie - Standard Romania) 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-7766 — Bug — [BE] - Media nu se calculeaza corect) 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-7870 — Bug — [FE] - Numarul matricol se suprapune peste numele elevului in Catalogul PDF) is still flagged as Dependency delay 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 / movement | Issue count | Calculation | Link |
|---|---|---|---|
| Planning snapshot raw list | 37 | Frozen planning export before metric exclusions | Open JQL |
| Sprint review / outcome snapshot raw list | 72 | Frozen review export before metric exclusions | Open JQL |
| Normalized sprint fact base | 66 | Deduplicated union used by metrics after canceled/cancelled exclusions | Open JQL |
| Metric planning baseline | 33 | Non-canceled issue keys present in the frozen planning snapshot | Open JQL |
| Metric outcome snapshot | 66 | Non-canceled issue keys present in the frozen sprint-review snapshot | Open JQL |
| Planned and still present at review | 33 | planning_snapshot_present = true and outcome_snapshot_present = true | Open JQL |
| Added after planning | 33 | planning_snapshot_present = false and outcome_snapshot_present = true | Open JQL |
| Planned but missing from review | 0 | planning_snapshot_present = true and outcome_snapshot_present = false | Open JQL |
| Metric-excluded canceled/cancelled rows | 6 | Rows preserved in audit but excluded from every numerator and denominator | Open JQL |
Planning and outcome are separate frozen moments. Raw snapshot counts can be larger than metric counts because canceled/cancelled rows stay in audit but leave all metric denominators.
Added after planning is snapshot-based: present in the outcome snapshot and absent from the planning snapshot. Planned but missing from review shows items that left the sprint snapshot before review.
| Metric | Value | Formula | Numerator / denominator | Denominator evidence |
|---|---|---|---|---|
| Visible sprint items | 66 | all rows in the outcome snapshot | 66/66 | Open denominator JQL |
| Delivered items | 37 | rows whose Sprint Outcome is Done | 37/66 | Open denominator JQL |
| Carry overs | 29 | rows whose Sprint Outcome is Carry Over or remained open in review | 29/66 | Open denominator JQL |
| Stories done | 2 | done items where issue type = Story | 2/37 | Open denominator JQL |
| Tasks done | 11 | done items where issue type = Task | 11/37 | Open denominator JQL |
| Bugs done | 20 | done items where issue type = Bug | 20/37 | Open denominator JQL |
| Entry kind mix | 33 / 33 / 0 | Planned / Added / Stretch counts across all visible sprint items | 66/66 | Open denominator JQL |
| Readiness mix | 27 / 39 / 0 | Ready / At risk / Not Ready counts across all visible sprint items | 66/66 | Open denominator JQL |
| Progress items behaving as intended | 0/1 | progress-intent items that carried as intended ÷ all progress-intent committed items | 0/1 | Open denominator JQL |
| Partial completion misses | 2 | carryover items whose miss reason is Partial completion | 2/29 | Open denominator JQL |
| Dependency / competing work misses | 0 | carryover items whose miss reason is Dependency delay | 0/29 | Open denominator JQL |
| Not-started misses | 19 | carryover items whose miss reason is Not started | 19/29 | Open denominator JQL |
| 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.