Sprint Pulse
Product Pulse — Team 2 ADS Q3 W30 - 27-31 Jul
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 DOCX
Executive summary
Yellow. The sprint closed 3 of 7 visible items, including 0 Stories, 1 Tasks, and 2 Bugs. Product movement was real, but the sprint was still noisy: 3 items entered after planning and 2 of them were closed. The main misses were concentrated in 4 carryovers.
Top-line metrics
| Metric | Value | How to read it |
|---|
| Visible sprint items | 7 | Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses |
| Delivered items | 3 | Items whose final outcome bucket is Done |
| Carry overs | 4 | Items not closed at sprint review |
| Delivered mix | 0 / 1 / 2 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 4 / 3 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 1 / 4 / 1 | 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 |
Stories done (0)
Below are the items marked Done in the sprint review snapshot, grouped by work-item type.
Carry overs / not delivered (4)
Blocker / miss pattern
| Metric | Value | How to read it |
|---|
| Partial completion | 3 | Carryovers blocked by partial completion |
| Dependency / competing work | 0 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 0 | Committed item never really got underway |
Data-quality caveats
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.
Traceability / drill-down
| 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 and fact-base list links
| Snapshot / movement | Issue count | Calculation | Link |
|---|
| Planning snapshot raw list | 4 | Frozen planning export before metric exclusions | Open JQL |
| Sprint review / outcome snapshot raw list | 7 | Frozen review export before metric exclusions | Open JQL |
| Normalized sprint fact base | 7 | Deduplicated union used by metrics after canceled/cancelled exclusions | Open JQL |
| Metric planning baseline | 4 | Non-canceled issue keys present in the frozen planning snapshot | Open JQL |
| Metric outcome snapshot | 7 | Non-canceled issue keys present in the frozen sprint-review snapshot | Open JQL |
| Planned and still present at review | 4 | 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.
Evidence artifacts
Use these files when you need to validate the exact rows and formulas behind a pulse claim.