Sprint Pulse

Product Pulse — University ADS Q3 W32 - 10-14 Aug

Planned sprint ADS Q3 W32 - 10-14 Aug • 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 8 of 15 visible items, including 2 Stories, 0 Tasks, and 6 Bugs. Product movement was real, but the sprint was still noisy: 2 items entered after planning and all of them were closed. The main misses were concentrated in 7 carryovers.

Top-line metrics

MetricValueHow to read it
Visible sprint items15Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses
Delivered items8Items whose final outcome bucket is Done
Carry overs7Items not closed at sprint review
Delivered mix2 / 0 / 6Stories / Tasks / Bugs delivered
Entry kind mix13 / 2 / 0Planned / Added during sprint / Stretch visible
Readiness mix7 / 8 / 0Ready / At risk / Not Ready across the normalized sprint fact base
Progress items behaving as intended3/3Progress items were expected not to finish in this sprint

Stories done (2)

Below are the items marked Done in the sprint review snapshot, grouped by work-item type.

Jira itemHow entered
ADS-7906 — [FE/BE] - Config -posibilitatea setarii mediei ca fiind confirmataPlanned
ADS-8058 — [BE/FE][UNI] - Generare serii si ani universitari bulkPlanned

Tasks done (0)

Jira itemHow entered

Bugs done (6)

Jira itemHow entered
ADS-7666 — accommodations-api: shared HTTP 500 burst on POST /api/v2/accommodations/dorms/list and related endpoints - 16 hits/20mAdded
ADS-8063 — [Prod][TUIASI][uni-api] Student search fails when search text contains an apostrophe - 4 errors/72hPlanned
ADS-8370 — [FE/BE] - Informatiile din anii anteriori pentru studenti care au trunchi comun nu sunt aduse pe filtru anual selectat atunci cand situatia scolara a unui astfel de studentPlanned
ADS-8440 — [FE/BE] - Asachi- Sesiunea 1 afișează note din Sesiunea 2 și paginarea nu se reseteazăPlanned
ADS-8443 — [AWS prod][University import] Existing Student role is logged as an errorPlanned
ADS-8470 — [FE/BE/] - Cazari - Obligatii de plataAdded

Carry overs / not delivered (7)

Jira itemWhy it carried
ADS-6142 — Story — [Registre Matricole] -US1.1 Creare volume si asociere studenti incadratiDependency delay
ADS-6438 — Task — [BE][UNI] - Sincronizare ID-uri Ani universitari/scolari - UNI/preuni - masterPartial completion
ADS-8159 — Story — [Burse] - US2 - Configurare bugete, PanouPartial completion
ADS-8160 — Story — [Burse] - US3 - Configurare bursePartial completion
ADS-8161 — Story — [Burse] - US4 - Alocare bursePartial completion
ADS-8176 — Story — [State de functii] - Functionalitati si fluxPartial completion
ADS-8179 — Story — [Registre Matricole] - US2 Incarcare atribute studenti pentru popularea registrelor matricolePartial completion

Blocker / miss pattern

MetricValueHow to read it
Partial completion6Carryovers blocked by partial completion
Dependency / competing work1Delivery slipped because attention or dependency landed elsewhere
Not started0Committed 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.

3 rows have Sprint Intent = Progress and remained open; they are treated as healthy continuation rather than finish misses.

Traceability / drill-down

Report elementHow to drill downTraceability mechanism
Delivered Stories / Tasks / BugsClick the section count rowsSnapshot-exact JQL by issuekey list
Carry overs / not deliveredClick the Carry overs countSnapshot-exact JQL by issuekey list
Miss pattern summaryClick each miss-pattern countSnapshot-exact JQL by issuekey list

Snapshot and fact-base list links

SnapshotIssue countLink
Planning snapshot raw list1212 issues in the planning snapshot
Sprint review / outcome snapshot raw list1515 issues in the Friday review snapshot
Normalized sprint fact base1515 issues used for metrics and drill-down

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

ArtifactLink
Issue audit registerOpen issue-level audit CSV
Metric lineageOpen metric lineage CSV
JQL traceability registerOpen JQL traceability CSV
Sprint metrics JSONOpen sprint metrics JSON

Use these files when you need to validate the exact rows and formulas behind a pulse claim.