6
STATUS REPORT as of February 28, 2014 This report is best view on screen and enlarged to 200%. Status: Status Trend: Project Completion: 63% Milestones Completed (since last report)(confirmed*): 9 Milestones Missed (since last report)(confirmed)*: 7 Milestones On/Behind Schedule (4-week outlook)(confirmed)*: 12 / 9 Milestones Imminent (within the next fortnight): 16 --- New Risks Opened (since last report): 4 Old Risks Closed (since last report): 7 New Issues Opened (since last report): 4 Old Issues Closed (since last report): 4 --- Days to Go-Live: 117 (as of Friday, Fri. 28, 2014) --- Note 1: Reports are also stored on the website - https://www.authpro.com/auth/OIT601/ --- Complete Colorado .com

CORE Project Status Report FEB w

Embed Size (px)

Citation preview

STATUS REPORT as of February 28, 2014

This report is best view on screen and enlarged to 200%.

Status:

Status Trend:

Project Completion: 63%

Milestones Completed (since last report)(confirmed*): 9 Milestones Missed (since last report)(confirmed)*: 7 Milestones On/Behind Schedule (4-week outlook)(confirmed)*: 12 / 9 Milestones Imminent (within the next fortnight): 16 --- New Risks Opened (since last report): 4 Old Risks Closed (since last report): 7 New Issues Opened (since last report): 4 Old Issues Closed (since last report): 4 --- Days to Go-Live: 117 (as of Friday, Fri. 28, 2014) --- Note 1: Reports are also stored on the website - https://www.authpro.com/auth/OIT601/ ---

Complete

Colorado

.com

STATUS REPORT as of February 28, 2014 Tier 1 (Top Priority) Key Issue 1: End-User Training Plan Delivery (late, WIP) Key Issue 2: Insufficient VPN Connectivity Key Issue 3: No Reporting Lead --- Key Risk 1: Excessive Project Crashing & Go-Live Schedule Risk Key Risk 2: End-User Training Material Development Timeliness Key Risk 3: End-User Training Delivery Quality Key Risk 4: Implementation of a statewide system in a decentralized and autonomous organization Key Risk 5: Lack of organization transformation preparedness Key Risk 6: Timely completion of Interface Development Key Risk 7: LDC solution delivery timeliness Key Risk 8: Heroism Dependency Risk --- Status Update Summary The CORE project is caught up in a flurry of activity in preparation go-live later this year. Unfortunately the project continues to suffer from a negative schedule variance which is simply a fancy way of stating the project is behind schedule. This variance has increased but only slightly. Actions are underway to both assess and deal with this. CGI continues to remain extremely dedicated to the project and is on-boarding a large number of personnel to address critical project activities. From a strategic perspective we have commenced “Go / No-Go” review sessions. The initial Go / No-Go review occurred on February 25, 2014 and the decision is to proceed with the project and the corrective actions in progress. Other Go / No-Go sessions will be held in March, April, and then again in June. As mentioned above the activities underway are many. CGI is conducting integrated system testing (IST). This is a test of the software divorced from state-specific processes. The purpose of which is to confirm the overall soundness of the application. IST has progressed well though interfaces remain a concern, not because of testing failure per se, but rather tardiness of interface development and thus having interfaces available for testing. OIT and CGI is working with all departments and agencies to address remaining development questions. In some cases departments face budgetary roadblocks for those interfaces managed by third-party vendors. In other cases the roadblocks are predecessor functional tasks still in progress. The functional teams are aware of this and are working rapidly to complete their work. Having stated these impediments progress on interfaces has improved significantly, however; they do remain behind schedule. We have set a “drop-dead” date of March 7, 2014. Our hope is all departments and agencies will have submitted system generated interface files that successfully integrate with CORE. Contingency plans may be necessary for those groups who do not make this date. Overall statewide network connectivity is a concern. In order to embrace all users, either from their offices or from remote locations, and including all approved non-employees (contractors) the State of Colorado will propose an alternative approach to network connectivity to CGI. This meeting will take place in one week. The project now has a User Acceptance Testing (UAT) Plan in place. Our UAT Lead (Christian Kalamula) is heavily engaged with the functional teams and the script development process. Scripts are predetermined testing steps designed to test every process relevant for the State of Colorado. In this way we confirm the suitability of application configuration for our use – and this is the key difference between IST (mentioned above) and UAT. UAT focuses specifically on our needs. State training personnel have been selected! They will participate in the CGI train-the-trainer program this month in preparation for their role in delivering training. In addition, CGI has an entire team of staff on site working on end-user training materials. Overall schedule risk contra the work remaining to be completed is the main concern of the project.

Complete

Colorado

.com

STATUS REPORT as of February 28, 2014

Complete

Colorado

.com

STATUS REPORT as of February 28, 2014

Complete

Colorado

.com

STATUS REPORT as of February 28, 2014

Complete

Colorado

.com

STATUS REPORT as of February 28, 2014

Complete

Colorado

.com