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. Count metrics link to snapshot-exact JQL result pages. Jira IDs in the report link to live Jira issues.
Download DOCXYellow. The sprint closed 7/12 visible items. The org roll-up absorbed noise reasonably well — 0/1 added items were closed — but predictability on committed work was only 63.6% (7/11), and bugs made up 57.1% of completed items. The main drag was execution system quality, not readiness: 0/4 carryovers had been marked Ready at planning time.
| Metric | Value | How to read it |
|---|---|---|
| Committed completion | 63.6% (7/11) | Planned items marked Done ÷ all planned committed items |
| Committed carryover | 36.4% (4/11) | Planned committed carryovers ÷ all planned committed items |
| Finish predictability | 63.6% (7/11) | Finish-intent planned items done ÷ all finish-intent planned items |
| Progress predictability | 0.0% (0/0) | Progress items that behaved as intended by carrying |
| Added-during-sprint load | 8.3% (1/12) | Added items ÷ all visible items |
| Added work closure | 0/1 | All added items marked Done |
| Reactive load (bug share) | 57.1% (4/7) | Completed bugs ÷ all completed work |
| Planning quality | 0.0% (0/11) | Committed items marked Ready ÷ all committed items |
| Workflow-truth mismatches | 0 | Items marked Done in review while workflow status remained non-final |
Across included teams, the sprint did not fail; it traded predictability for responsiveness. 0/1 added items were closed, but that responsiveness came with 57.1% bug share and diluted committed completion.
The miss pattern is concentrated: 2 partial-completion carryovers, 1 dependency-driven misses, and 0 committed items that never really started.
Most misses were not caused by poor readiness. 0 of the 4 carryovers had been marked Ready, so the stronger hypothesis is breakdown, sequencing, and capacity protection rather than simple scoping immaturity.
| Type | Planned | Added | Stretch | Unclear | Total done | Done % |
|---|---|---|---|---|---|---|
| Story | 0 | 0 | 0 | 0 | 0 | 0.0% |
| Task | 3 | 0 | 0 | 0 | 3 | 42.9% |
| Bug | 4 | 0 | 0 | 0 | 4 | 57.1% |
| Signal | Value | Why it matters |
|---|---|---|
| Committed items | 11 | Explicit promise set |
| Committed done | 7 | Closed as promised |
| Committed carry over | 4 | Unfinished promise |
| Committed items marked Ready | 0 | Planning-quality input |
| Carryovers marked Ready | 0 | Ready did not guarantee finish |
| Carryovers not started | 0 | Execution focus gap |
| Carryovers started but unfinished | 0 | Work moved, but did not close |
| Jira item | Owner | Status | Why it carried |
|---|---|---|---|
| ADS-6662 — Story — [Catalog][Situatie scolara] -US5 Download doc | Achim Stefan | Carry Over | Partial completion |
| ADS-6835 — Story — [Admitere v2] [US1.3] -Editare medie admitere single | George Murgoci | Missing from outcome snapshot | Missing from outcome snapshot |
| ADS-6910 — Bug — [BE-PHP][Cazari] - Soldul de pe fisa studentului nu corespunde cu cel de pe student | Ionut Ciolan | Carry Over | Partial completion |
| ADS-7179 — Bug — [BE][Asachi] - Verificare note introduse in sesiunea 1 | andrei.alexandru | Carry Over | Dependency delay |
| Pattern | Count | What it suggests |
|---|---|---|
| Partial completion | 2 | Breakdown / sizing / stage-gating was not tight enough |
| Dependency delay | 1 | Capacity protection or dependency timing created slip |
| Not started | 0 | A committed item remained outside execution focus |
| In Progress / Code Review carryovers | 0 | Most misses were moving, but not closing |
Items marked Done in the sprint-review field while Jira workflow status was still non-final.
| Jira item | Status | Intent |
|---|---|---|
| None |
| Question | Why this matters | What evidence to ask for |
|---|---|---|
| Why did committed items carry over despite planning readiness? | This tests execution quality rather than just scope quality. | Show carryovers split by progress continuation, dependency, and not-started. |
| Are Progress items being managed intentionally? | Progress items are allowed to continue, but the continuation should be visible and controlled. | Show the original slice and the specific landing expectation for each item. |
| Is added work a healthy responsiveness level or chronic interruption? | High responsiveness can hide systemic instability and diluted predictability. | Show which added items were urgent/reactive versus discretionary scope change. |
| Can we trust Done in review when workflow is still non-final? | Workflow-truth gaps reduce trust and make completion easy to game. | Show the exact mismatches and the completion rule to enforce next sprint. |
Included teams in this org pulse: University.
Usage note: start with the top-line metrics, then use the traceability links to answer these questions with issue-level evidence.
| 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 |
These companion artifacts keep the pulse debuggable when a leader wants the exact rows behind a metric or a count.