Attachment G IVV Dashboard Rep

Report As of Date: mm/dd/yyyy

Critical Project Review Panel Report

(DATE)

(As of Date) (Project Name)

Company Name, Address, Phone

GENERAL INFORMATION

OVERALL PROJECT HEALTH RATING

Agency Name:

Panel Review Meeting Date:

Project Name:

Project Reporting Period:

Original Project Budget:

Executive Summary

Current Project Budget:

Project Start Date:

DDI Start Date

GO-Live Date

Project End Date:

Project Phase:

Project Description

PROJECT STATUS INDICATORS - Trend values are “+” “-“ or ”N/C” . Comments must be brief and high-level.

OPTIONAL STATUS INDICATORS AS APPLICABLE TO PROJECT - Trend values are “+” “-“ or ”N/C” . Comments must be brief and high-level.

Report Details Communication Measures:

· A communications plan exists which includes all project stakeholders, key communication needs, frequency/timing of communications and communications method

· Communication feedback loops are in place to validate that communication is successful

· The communications plan is being followed

Observations:

Recommendations:

Cost Measures:

· Confident that budget contingency amount is sufficient

· Sustainability model is defined and regularly reviewed

· Project-to-date costs are meeting expectations

· Budget and actuals are tracked at an appropriate detail level

· Contract invoices are validated against accepted deliverables

· For non-fixed price contracts: cost variance is tracked against vendor’s cost baseline

· Technical Assessment: Include financial costs such as technical consulting, licenses, hosting, migration devices, cloud services etc.

Observations:

Recommendations:

Issue Management Measures:

· Issue Management Plan is defined

· Issue management is effective

· Escalation path is in place for all issues

· Issues are resolved timely

· Impact of issues to cost, scope, schedule, quality

· Include Technical Issues, if any

Observations:

Recommendations:

Quality Measures:

· Deliverable acceptance criteria defined and followed

· Quality of deliverables reviewed during last reporting period was acceptable

· Overall client satisfaction with quality of work products to date

· Quality criteria are well defined

· Defect criteria and reporting processes are defined and followed

Risk Management

· Risk management plan is defined

· Risk management process is in place and followed

· Response strategies for risks are documented

· Level of risk carried by the project as determined by Impact and Probability of Occurrence

· Timely risk reviews and updates are occurring

· Include Technical Risks. May include new technology used, technical skillset availability, Hosting Risks, Integration Risks as examples

Observations:

Recommendations:

Schedule Measures:

· Schedule management plan is defined

· Assessment of the effectiveness of the schedule

· Schedule is baselined

· Performance against the schedule as indicated by (SPI)

· Changes to baseline schedule are being managed.

Governance

· Governance Management Plan is defined

· Roles and responsibilities are identified and maintained

· Decision-making and escalation processes are developed and followed consistently

· Integration with other governing bodies identified and adhered to (financial, data management, etc.)

· Decisions are made in a timely manner at the appropriate level

· Meetings are being held regularly with required participation

Observations:

Recommendations:

Organizational Change Management (OCM) (As required by OCGA (Code Section 50-29-3)) Measures:

· An executable OCM strategy is defined and approved

· Level of training for customers/users is Identified

· Stakeholder analysis has been conducted and is updated regularly

· A risk assessment of organizational change is completed

· OCM has a resource assigned as owner with sufficient resources.

· Communication strategy is defined for acceptance of the change

· Training strategy(ies) is defined and incorporated into the integrated project schedule

Operational Readiness

· Operational Documentation is in place such as Runbooks, Support Scripts, Support Roles

· Criteria for go live is defined, documented and reviewed regularly

· Implementation (Deployment) Checklist is prepared

· Confident that a plan is ready to support the implementation day-one and ongoing support

· Confident that the right support resources are in place after go-live

Observations:

Recommendations:

Vendor Management Measures:

· State resource is assigned to manage contract terms

· The vendor reports to a state resource

· All vendor contract changes and decisions are approved by the state

· Vendor deliverables are clearly defined and can be tracked to the needs of the project

· Multiple vendors are managed by an Integrator

· Contract Performance (Schedule and Budget) is tracked and reported

Resource Management

· Project resource management plan is defined including all necessary resources (people, equipment, software, space etc.)

· Cross functional/project resource needs are identified (vendors, internal, external)

· Required skillsets are identified

· Resource acquisition processes and plans are identified (ie. RFS)

Observations:

Recommendations:

v6.3 Georgia Technology Authority IV&V Document: Critical Project Review Panel Report template 5/19/2021 1 image1.png