Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.


The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

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.12 Conduct Requirements Fit-Gap Analysis
3.11 Finalize Requirements
3.13 Finalize Target State Systems Environment
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Selection Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective: Understand gaps between customer requirements & provider’s standard solution and processes and develop gap solutions to inform migration approach, timeline, & revised cost estimates.

Phase 3 GuidanceLegend - Customer, Provider, Shared
1. Identify where functional and technical (e.g., security, interfaces) requirements can be met by the provider’s standard solution and where gaps may exist using the baselined Requirements Traceability Matrix (RTM) (P)
2. Conduct stakeholder validation sessions to review the fit-gap analysis. A sample fit-gap process kick-off is available here that can be used to guide agencies (S)
3. Design gap solutions with options for configuration changes, enhancements, and processes changes and review with the customer (P)
4. Select the desired solution to resolve each gap (S)
5. Document gaps and proposed solutions in Gap Analysis Report (P)
6. Use gap solutions to inform migration and release approach, schedule, and revised cost estimate (S)
7. Manage requirements through the RTM and PMO change control processes as agreed upon in the Requirements Management Plan and PMO governance (P)
8. Report updates in governance meetings and Status Reports/Dashboards (S)

• Provider’s Standard Solution and Requirements

• Gap Analysis Report
• Executive Sponsor (C, P)
• Business Owner (C, P)
• Program Manager (C, P)
• Requirements Lead (C, P)
• Technical Lead/Solution Architect (C, P)
• Functional SME (C, P)
• Technical SME (C, P)
• Managing Partner/Service Area Sponsor (Service Area)

Best Practice
• Assess functional, technical, and operational requirements as part of the fit-gap analysis
• Develop a detailed approach for the fit-gap with a Business Process Reengineering (BPR) Statement document that includes an Overview, BPR Vision, fit-gap Purpose and Objectives, and defines exit/success criteria for the process. A sample fit-gap process kick-off guide is available here
• Use live demonstrations for fit-gap review sessions
• Document gaps using formal gap ID forms and assess consensus with feedback surveys. A sample gap ID form is available here
• Use the Gap Analysis Report to identify the potential opportunities to standardize business processes across divisions and offices