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 1: Readiness
1.12 Review Standard Business Capabilities & Document Initial Business
1.11 Develop Initial Target State Concept of Operations and Scope of Services
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Customer Readiness Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective: Document business capabilities, mission critical, and unique capabilities of the customer organization to support the fit-gap analysis.

Phase 1 GuidanceLegend - Customer, Provider, Shared
1. Review Standard Business Capabilities previously defined by Government-wide Standards working group provided through the Federal Integrated Business Framework (FIBF) website (C)
2. As needed, document additional capabilities referencing the authoritative source and prioritize must-have versus nice-to-have capabilities against standard capabilities (C)
3. Identify Service Area Lead through the FIBF website and discuss additional capabilities identified in step 2 above with the Service Area Lead (C)
4. Validate capabilities with Business Owners and perform initial baselining (C)
5. Report updates in governance meetings and Status Reports/Dashboards(C)
6. Define requirements and management processes and document in the Requirements Management Plan (C)

• Vision
• Target State Concept of Operations
• Target State Systems Environment
• Government-wide Standards Defined through FIBF

• Requirements Management Plan
• Business Needs Workbook
• Business Capabilities
Stakeholders Update
• Executive Sponsor (C)
• Executive Sponsor (C)
• Business Owner (C)
• Program Manager (C)
• PMO Lead (C)
• Functional Lead (C)
• Technical Lead/Solution Architect (C)
• Requirements Lead (C)
• Functional SME (C)
• Technical SME (C)
• Service Area Lead (C)

Best Practice
• Define capabilities within the customer organization before engaging a provider to communicate needs in a consistent manner
• Provide criteria to define mission critical versus nice-to-have capabilities to enable improved provider selection
• Provide training to Subject Matter Experts (SMEs) on requirements processes and how to define, communicate, and document mission critical requirements
• Obtain a robust requirements management tool or process to manage requirements throughout the migration, including a robust change control process