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.

Technology

Task Activities

  1. Shared

    Update Requirements Management Plan and processes based on provider’s approach

  2. Customer

    Share updates to documentation of requirements, Target State Systems Environment, and Target State Concept of Operations with provider

  3. Shared

    Create a joint Requirements Traceability Matrix (RTM)

  4. Shared

    Prioritize mission critical and nice-to-have requirements against standard requirements and provider capability, and capacity in the RTM

  5. Shared

    Finalize requirements with Business Owners and baseline the RTM

  6. Shared

    Report updates in governance meetings and Status Reports/Dashboards

3.9 Best Practices

  • Conduct system demonstrations and Conference Room Pilots 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 life cycle
  • Validate requirements against the FIBF and ensure requirements are documented to allow for effective testing
  • Use the Requirements Traceability Matrix (RTM) to align, categorize, and prioritize outcome focused requirements with applicable Service Area standard requirements based on mission need and legislation/policy. Define and reference the specific source legislation/policy document(s) for each requirement and include requirement's status (i.e. awaiting approval, approved, rejected, or deferred)

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