Sprint Pulse
Product Pulse — Team 2 ADS Q3 W28 - 13-17 Jul
Planned sprint ADS Q3 W28 - 13-17 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 5 of 15 visible items, including 0 Stories, 3 Tasks, and 2 Bugs. Product movement was real, but the sprint was still noisy: 10 items entered after planning and 5 of them were closed. The main misses were concentrated in 10 carryovers.
Top-line metrics
| Metric | Value | How to read it |
|---|
| Visible sprint items | 15 | Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses |
| Delivered items | 5 | Items whose final outcome bucket is Done |
| Carry overs | 10 | Items not closed at sprint review |
| Delivered mix | 0 / 3 / 2 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 5 / 10 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 3 / 11 / 1 | Ready / At risk / Not Ready across the normalized sprint fact base |
| Progress items behaving as intended | 5/5 | Progress items were expected not to finish in this sprint |
Delivered work mix
| Type | Planned | Added | Stretch | Unclear | Total done | Done % |
|---|
| Story | 0 | 0 | 0 | 0 | 0 | 0.0% |
| Task | 0 | 3 | 0 | 0 | 3 | 60.0% |
| Bug | 0 | 2 | 0 | 0 | 2 | 40.0% |
Stories done
Below are the items marked Done in the sprint review snapshot, grouped by work-item type.
Carry overs / not delivered
Blocker / miss pattern
| Metric | Value | How to read it |
|---|
| Partial completion | 6 | Carryovers blocked by partial completion |
| Dependency / competing work | 0 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 4 | 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.
5 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
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.
Evidence artifacts
Use these files when you need to validate the exact rows and formulas behind a pulse claim.