Skip to main content

M3 Framework Introduction M3 Framework Overview M3 Phase 0 - Assessment M3 Phase 1 - Readiness M3 Phase 2 - Selection M3 Phase 3 - Engagement M3 Phase 4 - Migration M3 Phase 5 - Operations M3 Resources
M3 Playbook > Phase 3: Engagement
3.4 Monitor and Control Program Execution
3.3 Update and Maintain Procurement Plans
3.5 Maintain and Execute Risk Processes
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Selection Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective: Monitor, measure, and report on program migration progress.

Phase 3 GuidanceLegend - Customer, Provider, Shared
Activities
1. Manage scope and program performance using Program Management Plan (S)
2. Manage Integrated Master Schedule (IMS) through weekly updates of activities, dates, duration, and dependencies (S)
3. Manage costs against the budget (S)
4. Manage and update HR/Staffing Plan as resources are on or off boarded or as needs change (S)
5. Manage and update the Independent Verification and Validation (IV&V) Plan (S)
6. Update program management documentation as necessary (S)
7. Initiate and perform change requests to address changes in schedule, scope, and requirements throughout the program through the Change Request Form, documenting changes through the Change Request Log (S)
 8. Develop and distribute Status Reports/Dashboards (S)
9. Hold status meetings to monitor status against milestones, issues, risks, and make decisions needed for work streams (S)
10. Escalate decisions and issues as needed through governance bodies (S)
11. Conduct executive briefings with organization leadership and oversight entities as necessary (S)
12. Develop Lessons Learned Report (S)

Inputs
• Program Charter
• Program Management Plan
• IMS
• IV&V Plan
• HR/Staffing Plan
• Governance Charter
• Status Reports/Dashboards

Outputs
• Program Management Plan
• Status Reports/Dashboards
• IV&V Plan
• Change Request Log
• Change Request Form		 • IMS
• Lessons Learned Report
Stakeholders
• Executive Sponsor (C, P)
• Business Owner (C, P)
• Program Manager (C, P)
• PMO Lead (C, P)
• PMO Team (C, P)
• Functional Lead (C, P)
• Technical Lead/Solution Architect (C, P)

Best Practice
• Include all migration activities and responsible parties in the IMS
• Implement weekly change control process to manage changes to the IMS to understand downstream impacts and associated risks
• Review and update the integrated program plan regularly and establish an integrated recurring meeting and status reporting cadence
• Utilize collaboration tools to the fullest extent in order to facilitate information sharing across the migration program
• Create a consolidated list of action items for the customer and provider