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.11 Finalize Requirements
3.10 Develop Training Plan
3.12 Conduct Requirements Fit-Gap Analysis
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Selection Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective: Perform knowledge transfer of requirements, validate requirements, baseline all standard & unique requirements w/approvals to inform fit-gap analysis.

Phase 3 GuidanceResponsible Party - Customer, Provider, Shared
1. Update Requirements Management Plan and processes based on provider’s approach (S)
2. Share updates to documentation of requirements, Target State Systems Environment, and Target State Concept of Operations with provider (C)
3. Create a joint Requirements Traceability Matrix (RTM) (S)
4. Prioritize mission critical and nice-to-have requirements against standard requirements and provider capability, and capacity in the RTM (S)
5. Finalize requirements with Business Owners and baseline the RTM (S)
6. Report updates in governance meetings and Status Reports/Dashboards (S)

• Business Needs Workbook
• Scope of Services
• Stakeholder Analysis
• As-Is Workforce Assessment Financial Management, Human Resources)

• Updated Requirements Management Plan
• Requirements Traceability Matrix
Stakeholders Update
• Executive Sponsor (C, P)
• Business Owners (C, P)
• Program Manager (C, P)
• Requirements Lead (C, P)
• Technical Lead/Solution Architect (C, P)
• Functional SMEs (C, P)
• Technical SMEs (C, P)
• Managing Partner/Line of Business Sponsor (Line of Business)

Best Practice
• Conduct system demonstrations and Conference Room Pilots (CRPs) to validate the solution meets the intended scope of services requirements
• Provide training to SMEs on requirements processes and how to define, communicate, and document requirements effectively (e.g ., essential, verifiable requirements)
• Provide criteria to define mission critical versus nice-to-have requirements to enable improved provider selection
• Use requirements management tool and establish requirements management approach that follows leading practices to increase consistency and enhance traceability throughout the program’s lifecycle
• Validate the requirements are testable