Skip to main content
M3 Playbook > Phase 3: Engagement > 3.11 Finalize Target State Systems Environment
Play Icon

3.11 : Finalize Target State Systems Environment

Technology
  1. Customer

    Transfer knowledge of As-Is Systems Environment, including required legacy system interfaces

  2. Shared

    Review initial Target State Environment; compare to provider’s standard solution to determine gaps

  3. Provider

    Develop options for technical gap solutions, include enhancements and required new interfaces

  4. Shared

    Assess gap solutions for cost / timeline impacts; document implications for release strategy

  5. Shared

    Finalize Target State Environment through technical review, if necessary

  6. Shared

    Define scope of implementation and at each release, if applicable

  7. Shared

    Report updates in leadership / governance meetings thru Status Reports/Dashboards

3.11 Lessons Learned

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

Stakeholders

Recommended stakeholders, inputs, & outputs may vary by implementation; however, agencies that contributed to this Playbook reported these factors as increasing the likelihood of success.

Customer

  • Program Manager
  • Business Owner
  • Functional Lead
  • Technical Lead/Solution Architect
  • Interface Lead
  • Functional SME
  • Technical SME

Provider

  • Program Manager
  • Business Owner
  • Functional Lead
  • Technical Lead/Solution Architect
  • Interface Lead
  • Functional SME
  • Technical SME

Inputs

Outputs

Return to top

USSM.GSA.gov

An official website of the General Services Administration

Looking for U.S. government information and services?
Visit USA.gov