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.

Https

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.

The Modernization and Migration Management (M3) Playbook has a new look! Explore our new features here.

M3 Playbook > Phase 3: Engagement > 3.10 Conduct Requirements Fit-Gap Analysis

3.10 Conduct Requirements Fit-Gap Analysis

Technology

Task Activities

  1. Provider

    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)

  2. Shared

    Conduct stakeholder validation sessions to review the Requirements Fit-Gap Analysis. A sample requirements fit-gap process kick-off is available for reference.

  3. Provider

    Design gap solutions with options for configuration changes, enhancements, and processes changes and review with the customer

  4. Shared

    Select the desired solution to resolve each gap

  5. Customer

    Document gaps and proposed solutions in the Requirements Fit-Gap Analysis

  6. Shared

    Use gap solutions to inform migration and release approach, schedule, and revised cost estimate

  7. Provider

    Manage requirements through the RTM and PMO change control processes as agreed upon in the Requirements Management Plan and PMO governance

  8. Shared

    Report updates in governance meetings, and Status Reports/Dashboards, informing QSMOs as necessary

3.10 Best Practices

  • Assess functional, technical, and operational requirements as part of the Requirements Fit-Gap Analysis
  • Technical requirements for the Requirements Fit Gap Analysis should align to the FIBF standards
  • 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 requirements fit-gap process kick-off is available for reference.
  • Use live demonstrations for requirements fit-gap review sessions
  • Document gaps using formal gap ID forms and assess consensus with feedback surveys. A sample gap ID form is available for reference.

Stakeholders

Customer

  • Executive Sponsor
  • Business Owner
  • Program Manager
  • Requirements Lead
  • Technical Lead/Solution Architect
  • Functional SME
  • Technical SME

Provider

  • Executive Sponsor
  • Business Owner
  • Program Manager
  • Requirements Lead
  • Technical Lead/Solution Architect
  • Functional SME
  • Technical SME

Inputs

Outputs