Sprint Pulse

Product Pulse — Team 2 ADS Q3 W29 - 20-24 Jul

Planned sprint ADS Q3 W29 - 20-24 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 14 visible items, including 0 Stories, 3 Tasks, and 1 Bugs. Product movement was real, but the sprint was still noisy: 4 items entered after planning and all of them were closed. The main misses were concentrated in 9 carryovers.

Top-line metrics

MetricValueHow to read it
Visible sprint items14Normalized sprint fact base: planning baseline plus outcome additions and planning-only misses
Delivered items5Items whose final outcome bucket is Done
Carry overs9Items not closed at sprint review
Delivered mix0 / 3 / 1Stories / Tasks / Bugs delivered
Entry kind mix8 / 4 / 2Planned / Added during sprint / Stretch visible
Readiness mix6 / 8 / 0Ready / At risk / Not Ready across the normalized sprint fact base
Progress items behaving as intended4/5Progress 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.

Jira itemHow entered

Tasks done (3)

Jira itemHow entered
ADS-6064 — [Internal] Export Clienti Adservio din Billing pentru import in NexusAdded
ADS-7343 — [Stiri] - Distribuie UpdatesPlanned
ADS-8319 — [Abonamente] - Rambursare 2969809Added

Bugs done (1)

Jira itemHow entered
ADS-8316 — [Prod][Billing/Frontend] Groups Marks hides eligible services beyond first 100 resultsAdded

Carry overs / not delivered (9)

Jira itemWhy it carried
ADS-4007 — Bug — [BE][Subscriptions] - Comportament ciudat featureflags in cazul in care sunt dezactivate subscriptiileNot started
ADS-4328 — Story — Headers in Mobile AppNot started
ADS-6159 — Story — Notification Center for MobilePartial completion
ADS-6201 — Story — Log formatting - node.js, subscriptionsNot started
ADS-6675 — Story — [Financiar] - Managementul penalitatilorPartial completion
ADS-7474 — Task — [FE] - Optimizare viteză de încărcare paginiPartial completion
ADS-7849 — Story — Stergere date S3Bug / rework pressure
ADS-8071 — Story — Teste automate flow SubscripțiiPartial completion
ADS-8223 — Bug — [Prod][AWS][ingress] POST /api/v2/fisiere/upload maps backend 400 to HTTP 500 - 10/72hNot started

Blocker / miss pattern

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

4 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

Snapshot / movementIssue countCalculationLink
Planning snapshot raw list10Frozen planning export before metric exclusionsOpen JQL
Sprint review / outcome snapshot raw list14Frozen review export before metric exclusionsOpen JQL
Normalized sprint fact base14Deduplicated union used by metrics after canceled/cancelled exclusionsOpen JQL
Metric planning baseline10Non-canceled issue keys present in the frozen planning snapshotOpen JQL
Metric outcome snapshot14Non-canceled issue keys present in the frozen sprint-review snapshotOpen JQL
Planned and still present at review10planning_snapshot_present = true and outcome_snapshot_present = trueOpen JQL
Added after planning4planning_snapshot_present = false and outcome_snapshot_present = trueOpen JQL
Planned but missing from review0planning_snapshot_present = true and outcome_snapshot_present = falseOpen JQL
Metric-excluded canceled/cancelled rows0Rows preserved in audit but excluded from every numerator and denominatorOpen 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.

Metric register addendum

MetricValueFormulaNumerator / denominatorDenominator evidence
Visible sprint items14all rows in the outcome snapshot14/14Open denominator JQL
Delivered items5rows whose Sprint Outcome is Done5/14Open denominator JQL
Carry overs9rows whose Sprint Outcome is Carry Over or remained open in review9/14Open denominator JQL
Stories done0done items where issue type = Story0/5Open denominator JQL
Tasks done3done items where issue type = Task3/5Open denominator JQL
Bugs done1done items where issue type = Bug1/5Open denominator JQL
Entry kind mix8 / 4 / 2Planned / Added / Stretch counts across all visible sprint items14/14Open denominator JQL
Readiness mix6 / 8 / 0Ready / At risk / Not Ready counts across all visible sprint items14/14Open denominator JQL
Progress items behaving as intended4/5progress-intent items that carried as intended ÷ all progress-intent committed items4/5Open denominator JQL
Partial completion misses4carryover items whose miss reason is Partial completion4/9Open denominator JQL
Dependency / competing work misses0carryover items whose miss reason is Dependency delay0/9Open denominator JQL
Not-started misses4carryover items whose miss reason is Not started4/9Open denominator JQL

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.