Why This Looks Different From a PMBOK Change Control Log
The Enrollment & Claims PM Suite uses a formal Change Control Log because that program's scope, cost, and schedule are baselined up front — any change to them requires a documented, approved change request. An Agile program doesn't baseline a detailed WBS the same way, so most day-to-day scope adjustment happens through backlog reprioritization — the Product Owner re-orders or re-scopes the backlog without a formal change request, because the backlog is expected to evolve. Formal change control still exists here, but it's reserved for changes that affect the program's baselined commitments: release dates, budget, or the Release 1/Release 2 scope boundary itself.
Two Paths
Backlog Reprioritization (no formal process)
- New story, re-estimate, or re-sequencing within already-approved scope
- Product Owner decides at Backlog Refinement or Sprint Planning
- Logged in the Product Backlog / Sprint Backlog — no separate approval needed
- Example: MCM-123's re-estimation from 5 to 8 points after a vendor-configuration finding
Formal Change Request (baseline impact)
- Anything that would move a release date, increase budget, or add/remove scope from Release 1 or Release 2's committed boundary
- Requires Sponsor approval, logged and traceable — same spirit as the PMBOK Change Control Log, adapted to Agile cadence
- Example: if the provider feedback request (MCM-155) had been pulled into Release 2's committed scope instead of staying a candidate backlog item, that would have required this path
Formal Change Log (This Program)
Three formal (baseline-impacting) changes were required over the life of the program — two cost-impact changes and one schedule-impact change, all approved. Every other scope adjustment stayed within backlog reprioritization. Full detail, including impact analysis and outcome-if-not-approved for each, is in the dedicated Change Control Log.
| Category | Count | Handled Via |
|---|---|---|
| Backlog reprioritizations / re-estimations | 2 logged (MCM-123 re-estimate, MCM-133 story split) | Backlog Refinement — see RAIDD Log, Decisions |
| Formal change requests (baseline impact) | 3 (CR-01, CR-02, CR-03) | Sponsor approval (+ Compliance co-approval for CR-03) — see Change Control Log |