Release Management. The system’s release schedule involves planning, approval for system outages from stakeholders, and management of the resources required to execute the schedule. A quarterly release schedule is required to meet operational availability requirements. The Contractor shall attend the monthly PMO release planning meeting and provide a proposed release plan identifying CRs for appropriate releases based on the problem management backlog assignments and PMO ranking. The Contractor shall provide status updates for ongoing release plans at the release planning meeting. The Contractor shall schedule, coordinate, plan, and implement approved releases with CM. The Contractor shall assign builds to appropriate software releases as identified in the GCSS-MC CMP and develop 30/60/90 day release schedules based upon assignment, prioritization, and scheduling, including refreshing the environments defined in Section 1.1. The Contractor shall maintain a PSS and Production Software Baseline Reports (PSBR) and track CRs or software releases by build per release, patch set, and clones provided as GFI. The Contractor shall gather approved CR and build-specific data by attending CAB and CCB meetings, Test Incident Reporting (TIR) meetings, testing hot-washes and applicable meetings to incorporate into an assignment, prioritization, and scheduling spreadsheet. The Contractor shall coordinate with the Government to schedule ad hoc system backups and database clones for promotion to solution development and test instances, and compile the 30/60/90 day release schedule. The Contractor shall prepare DD Form 1149 and track distribution of clones and clone contents (builds). The Contractor shall identify requirements and propose an associated schedule for technical refresh of these environments.
Appears in 2 contracts