Risks, Assumptions, Issues, Dependencies, and Decisions — the same RAIDD structure as the Enrollment & Claims PM Suite, but populated the way it actually gets used on an Agile program: dependencies are mostly cross-team (tracked here and on the Jira board), and several entries trace directly back to specific ceremonies you've already seen.
4
Risks
3
Assumptions
2
Issues
3
Dependencies
5
Decisions
Risks
Uncertain future events that could affect the program.
| ID | Risk | Severity | Mitigation | Status |
|---|---|---|---|---|
| R-01 | Full historical data migration (Sprint 7) could surface data-quality issues in legacy archive records, requiring remediation time | Medium | Pre-cutover validation report + spot-check process (same pattern used successfully for Release 1's active-patient migration) | Closed — migration completed within estimate |
| R-02 | Third-party video SDK's screen-share feature could require additional vendor configuration not originally scoped | Medium | Spike performed during Sprint 3 refinement; re-estimated MCM-123 from 5 to 8 pts | Closed — realized as a scope/estimate change, not a schedule risk |
| R-03 | Cross-team dependencies surfacing too late in a sprint to resolve without schedule impact | Medium | Sprint 2 retro actions — dependency owner field, standing Scrum-of-Scrums agenda item | Closed — confirmed effective at Sprint 3 retro |
| R-04 | Team cost run-rate tracking slightly ahead of planned burn heading into the highest-effort remaining sprint | Medium | Monitored weekly against Sprint 7–8 forecast; two short-term contractors approved for Sprint 7 remediation only (see CR-02, +$42,000) | Closed — program finished within budget |
Assumptions
Conditions taken as true for planning purposes.
| ID | Assumption | Validated? |
|---|---|---|
| A-01 | The video SDK vendor's existing BAA (executed during vendor selection) covers the telehealth use case without renegotiation | Confirmed — T. Brannigan, Sprint 3 Planning |
| A-02 | Both teams can sustain a consistent 2-week sprint cadence without holiday/PTO disruption beyond what was planned for in capacity | Held true |
| A-03 | The pilot patient cohort (Release 1) is representative enough to surface major usability issues before full rollout | Held true — no major issues surfaced beyond MCM-155 feature request |
Issues
Problems that have already occurred and need resolution.
| ID | Issue | Severity | Resolution | Status |
|---|---|---|---|---|
| I-01 | MCM-111 blocked in Sprint 2 waiting on Anchor's availability engine (MCM-160) code review | Medium | Same-day escalation between Engineering Leads; review completed within hours | Closed, Sprint 2 |
| I-02 | MCM-181 (rollback runbook) descoped from formal Sprint 5 board tracking, completed manually instead | Low | Accepted as a one-off; no process change needed since it didn't recur | Accepted |
Dependencies
Cross-team or external dependencies tracked at the program level (in addition to being linked on the Jira board).
| ID | Dependency | Owner | Status |
|---|---|---|---|
| D-01 | Falcon's booking/reschedule UI (MCM-111) depends on Anchor's availability engine API (MCM-160) | A. Singh (Anchor) | Resolved, Sprint 2 |
| D-02 | Falcon's video join flow (MCM-120) depends on Anchor's video SDK integration (MCM-121) | A. Singh (Anchor) | Resolved, Sprint 3–4 |
| D-03 | Release 2 cutover depends on Compliance sign-off of the full historical migration validation report | T. Brannigan (Compliance) | Resolved, Sprint 8 |
Decisions
Formal program-level decisions, each traceable to the ceremony or meeting where it was made.
| ID | Decision | Made At | Made By |
|---|---|---|---|
| DEC-01 | Definition of Done updated to require clinical workflow sign-off for scheduling/visit-launch/notes-handoff stories | Program Kickoff | Dr. L. Nguyen, endorsed by C. Tyrrell |
| DEC-02 | Compliance review checkpoint added before both Release 1 and Release 2 (not a single end-of-program gate) | Program Kickoff | T. Brannigan |
| DEC-03 | Split MCM-133 into a data-mapping story and a UI story to reduce single-sprint delivery risk | Sprint 3 Backlog Refinement | C. Tyrrell + both teams |
| DEC-04 | Hold Release 1 to the pilot cohort rather than full rollout immediately after MVP launch | Sprint 5 Review | M. Delacroix (Sponsor) |
| DEC-05 | Release 2 Go/No-Go: GO — all acceptance criteria, compliance, and clinical sign-offs met | Sprint 8 Review | M. Delacroix (Sponsor) |
| DEC-06 | Original 13-person, $1,850,000 resource estimate corrected to a 28-person, $3,617,000 delivery team — the initial plan staffed leads and one developer per platform but no real bench (no UX/UI design, no dedicated Provider Console frontend developer, no data migration owner, no QA test bench beyond team leads, no Business Analyst, no cross-team Solutions Architect). Corrected before Sprint 1 Planning so the real team, not the estimate, executed the program. | Program Kickoff / pre-Sprint 1 | C. Tyrrell, approved by M. Delacroix (Sponsor) |