Aggregated sprint ADS Q1-26 W-14 • deduplicated roll-up across included teams
This org roll-up aggregates deduplicated frozen issue facts across 1 team snapshots, then applies the same metric definitions and drill-down model. Counts in metric tables link to snapshot-exact JQL result pages.
Download DOCXYellow. The sprint closed 7 of 12 visible items, including 0 Stories, 3 Tasks, and 4 Bugs. Product movement was real, but the sprint was still noisy: 1 items entered after planning and 0 of them were closed. The main misses were concentrated in 5 carryovers.
| Metric | Value | How to read it |
|---|---|---|
| Visible sprint items | 12 | All rows in the outcome snapshot used for this retrospective |
| Delivered items | 7 | Items whose final outcome bucket is Done |
| Carry overs | 5 | Items not closed at sprint review |
| Delivered mix | 0 / 3 / 4 | Stories / Tasks / Bugs delivered |
| Entry kind mix | 11 / 1 / 0 | Planned / Added during sprint / Stretch visible |
| Readiness mix | 0 / 0 / 0 | Ready / At risk / Not Ready in the outcome snapshot |
| Progress items behaving as intended | 0/0 | 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 |
|---|
| Jira item | Why it carried |
|---|---|
| ADS-6662 — Story — [Catalog][Situatie scolara] -US5 Download doc | Partial completion |
| ADS-6835 — Story — [Admitere v2] [US1.3] -Editare medie admitere single | Missing from outcome snapshot |
| ADS-6910 — Bug — [BE-PHP][Cazari] - Soldul de pe fisa studentului nu corespunde cu cel de pe student | Partial completion |
| ADS-7179 — Bug — [BE][Asachi] - Verificare note introduse in sesiunea 1 | Dependency delay |
| ADS-7234 — Bug — [BE][Asachi][Catalog-Situație școlara] - Nu se calculeaza media |
| Metric | Value | How to read it |
|---|---|---|
| Partial completion | 2 | Carryovers blocked by partial completion |
| Dependency / competing work | 1 | Delivery slipped because attention or dependency landed elsewhere |
| Not started | 0 | Committed item never really got underway |
This org roll-up is retrospective only and uses the planning snapshot for baseline fields and the outcome snapshot for actuals.
Included teams in this org pulse: University.
One Done row (ADS-7077 — Task — [QA][Financiar] - E2E testing UMS) 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 | Issue count | Link |
|---|---|---|
| Planning snapshot full list | 11 | 11 issues used for planning baseline |
| Sprint review / outcome snapshot full list | 11 | 11 issues reviewed at sprint review |
These links are snapshot-exact JQL lists, intended for drill-down and debugging.
| 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.