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.13 Finalize Target State Systems Environment
3.12 Conduct Requirements Fit-Gap Analysis
3.14 Develop Technical Strategy
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 as-is environment and finalize the Initial Target State Systems Environment that capture all required interfaces, application, security/privacy, and data layers.

Phase 3 GuidanceLegend - Customer, Provider, Shared
Activities
1. Perform knowledge transfer to provider to gain an understanding of the customer’s As-is Systems Environment including which interfaces to legacy systems will be required (C)
2. Review Initial Target State Systems Environment and compare against the provider’s standard solution to determine where gaps exist (S)
3. Develop solutions for technical gaps where enhancements are required to systems and infrastructure and where new interfaces will be required (P)
4. Assess gap solutions of technical environment based on cost and timeline implications and document impacts to release strategy (S)
5. Finalize Target State Systems Environment, through technical reviews if necessary, to define the scope of the migration and at each release, if applicable (S)
6. Report updates in governance meetings and Status Reports/Dashboards (S)

Inputs
• Vision and Business Case
• Requirements Traceability Matrix (RTM)
• Existing Enterprise Architecture Documents & System Specifications
• Target State Systems Environment

Outputs
• Validated and Updated As-Is Systems Environment
• Target State Systems Environment
Stakeholders Update
• Program Manager (C, P)
• Business Owner (C, P)
• Functional Lead (C, P)
• Technical Lead/Solution Architect (C, P)
• Interface Lead (C, P)
• Functional SME (C, P)
• Technical SME (C, P)

Best Practice
• Leverage the current systems architecture and specification documents as a starting point
• Document critical interfaces between legacy systems and new systems including detailed data requirements and network requirements