Office of the Chief Technology Officer: Program Completion and Closeout
DC Home Mayor DC Guide Residents Business Visitors DC Government Kids

Office of the Chief Technology Officer

OCTO HOME
OCTO HOME
SERVICES
ABOUT OCTO
INFORMATION
SERVICES
ONLINE SERVICE
  REQUESTS

INFORMATION
ONLINE SERVICE
  REQUESTS

About OCTO
How to Reach Us
Ask the CTO
FOIA Requests
News Room
Employment
  Opportunities

Site Map
Performance
CityDW
DC GIS
DC-NET
DC-WARN
ASMP
HSMP
Photo Gallery
Policies, Guidelines, &
  Procedures

DC IT Investment Board
Program Management
  Standards

Web Standards
  and Style

CTO's Biography
Mission & Goals
Organizational Chart

Program Completion and Closeout
 
The completion and closeout process ensures that all contractual performance of outside vendors have meet all contractual requirements.
  1. Create an Acceptance Management Plan. The acceptance management plan ensures that program deliverables are formally accepted and meet all agreed upon contractual requirements. The following items should be included in the acceptance management plan:
    • Deliverables according to the signed contract or SOW
    • Delivery schedules indicating dependencies as well as absolute dates
    • Terms of delivery
    • Formal recognition of delivery
    • Negotiated corrections
    • Determination of acceptance or rejection

  2. Implement the Transition to Operations Plan. Finalize and implement the transition to operations plan that identifies all the new and modified application system assets resulting from the program that will be required by the operations team to continue its support work effectively. These assets include:
    • System description
    • Timeline for transition to operations
    • Impact of each requirement provided (resources, skill levels, effort involved)
    • Project deliverables list
    • Application module specifications
    • System test acceptance and certification report
    • Completed source code
    • Clearly described error messages and conditions
    • Operations budget and resource requirements
Page 1 of 2    Go To Previous Page  1  2  Go To Next Page