← Agile/Scrum Suite 11 · Ceremonies

Backlog Refinement Notes

Download Word
DateFeb 18, 2026
SprintSprint 3, mid-sprint
FacilitatorC. Tyrrell
AttendeesBoth teams (subset — leads + 2 devs each)

Purpose

Weekly refinement session to keep the next 1–2 sprints' worth of backlog at Definition of Ready. This session focused on splitting a large story in Epic 4 (Provider Console) and re-estimating two stories after new information from the video SDK vendor.

Story Split: MCM-133

The team flagged MCM-133 ("provider visit notes push directly into the ACME EHR") as too large and too risky to safely complete inside a single sprint — the EHR integration involves both a data-mapping problem and a UI problem that don't need to ship together.

BeforeMCM-133 — Provider visit notes push directly into the ACME EHR without re-entry (13 pts, single story)
After — split into two stories MCM-133a — Build and test the EHR data-mapping/API integration for visit notes (8 pts)
MCM-133b — Provider-facing UI: review and confirm notes before they push to the EHR (5 pts)

Rationale: 133a can be developed and validated against the EHR sandbox independently of any UI work, letting Anchor make progress even if the UI design isn't finalized. Both were re-confirmed at Definition of Ready and scheduled for Sprint 6.

Re-Estimation

IDStoryOld EstimateNew EstimateReason
MCM-121Video SDK integration w/ audio fallback1313Re-confirmed, no change — vendor confirmed BAA coverage as assumed
MCM-123Provider screen-share of lab results/images during a visit58Vendor SDK requires a separate screen-share entitlement/config not initially scoped — increased after a spike

Definition of Ready Check — Stories Entering Sprint 4 Candidate Pool