Planned sprint ADS Q3 W30 - 27-31 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 10 of 21 visible items, including 1 Stories, 0 Tasks, and 9 Bugs. Product movement was real, but the sprint was still noisy: 3 items entered after planning and all of them were closed. The main misses were concentrated in 11 carryovers.
| Metric | Value | How to read it |
|---|---|---|
| Visible sprint items | 21 | Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses |
| Delivered items | 10 | Items whose final outcome bucket is Done |
| Carry overs | 11 | Items not closed at sprint review |
| Delivered mix | 1 / 0 / 9 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 16 / 3 / 2 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 4 / 17 / 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 |
Below are the items marked Done in the sprint review snapshot, grouped by work-item type.
| Jira item | How entered |
|---|---|
| ADS-7952 — [Burse] - US1 - Implementare mecanism Atribute | Planned |
| Jira item | How entered |
|---|
| Metric | Value | How to read it |
|---|---|---|
| Partial completion | 6 | Carryovers blocked by partial completion |
| Dependency / competing work | 3 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 1 | 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 / movement | Issue count | Calculation | Link |
|---|---|---|---|
| Planning snapshot raw list | 18 | Frozen planning export before metric exclusions | Open JQL |
| Sprint review / outcome snapshot raw list | 21 | Frozen review export before metric exclusions | Open JQL |
| Normalized sprint fact base | 21 | Deduplicated union used by metrics after canceled/cancelled exclusions | Open JQL |
| Metric planning baseline | 18 | Non-canceled issue keys present in the frozen planning snapshot | Open JQL |
| Metric outcome snapshot | 21 | Non-canceled issue keys present in the frozen sprint-review snapshot | Open JQL |
| Planned and still present at review | 18 | planning_snapshot_present = true and outcome_snapshot_present = true | Open JQL |
| Added after planning | 3 | 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 | 0 | 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 | 21 | all rows in the outcome snapshot | 21/21 | Open denominator JQL |
| Delivered items | 10 | rows whose Sprint Outcome is Done | 10/21 | Open denominator JQL |
| Carry overs | 11 | rows whose Sprint Outcome is Carry Over or remained open in review | 11/21 | Open denominator JQL |
| Stories done | 1 | done items where issue type = Story | 1/10 | Open denominator JQL |
| Tasks done | 0 | done items where issue type = Task | 0/10 | Open denominator JQL |
| Bugs done | 9 | done items where issue type = Bug | 9/10 | Open denominator JQL |
| Entry kind mix | 16 / 3 / 2 | Planned / Added / Stretch counts across all visible sprint items | 21/21 | Open denominator JQL |
| Readiness mix | 4 / 17 / 0 | Ready / At risk / Not Ready counts across all visible sprint items | 21/21 | Open denominator JQL |
| Progress items behaving as intended | 3/3 | progress-intent items that carried as intended ÷ all progress-intent committed items | 3/3 | Open denominator JQL |
| Partial completion misses | 6 | carryover items whose miss reason is Partial completion | 6/11 | Open denominator JQL |
| Dependency / competing work misses | 3 | carryover items whose miss reason is Dependency delay | 3/11 | Open denominator JQL |
| Not-started misses | 1 | carryover items whose miss reason is Not started | 1/11 | 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.