Jurris.COM
Section 13300.5 Of Article 1. General From California Government Code >> Division 3. >> Title 2. >> Part 3. >> Chapter 3. >> Article 1.
13300.5
. (a) The Legislature finds and declares that the project of
the FISCal Project to modernize the state's internal financial
systems is a critical project that must be subject to the highest
level of oversight. According to the Department of Technology, the
size and scope of this modernization and automation effort make this
project one of the highest risk projects undertaken by the state.
Therefore, the Legislature must take steps to ensure it is fully
informed as the project is implemented. It is the intent of the
Legislature to adopt additional reporting requirements for the FISCal
Project Office to adequately manage the project's risk and to ensure
the successful implementation of this effort.
(b) The FISCal Project Office shall report to the Legislature, by February 15 of each year, an update on the project. The report shall include all of the following:
(1) An executive summary and overview of the project's status.
(2) An overview of the project's history.
(3) Significant events of the project within the current reporting period and a projection of events during the next reporting period.
(4) A discussion of mitigation actions being taken by the project for any missed major milestones.
(5) A comparison of actual to budgeted expenditures, and an explanation of variances and any planned corrective actions, including a summary of FISCal project and staffing levels and an estimate of staff participation from partner agencies.
(6) An articulation of expected functionality and qualitative benefits from the project that were achieved during the reporting period and that are expected to be achieved in the subsequent year.
(7) An overview of change management activities and stakeholder engagement in the project, including a summary of departmental participation in the FISCal project.
(8) A discussion of lessons learned and best practices that will be incorporated into future changes in management activities.
(9) A description of any significant software customization, including a justification for why, if any, customization was granted.
(10) Updates on the progress of meeting the project objectives.
(c) The initial report, due February 15, 2013, shall provide a description of the approved project scope. Later reports shall describe any later deviations to the project scope, cost, or schedule.
(d) The initial report shall also provide a summary of the project history from Special Project Report 1 to Special Project Report 4, inclusive.
(e) This section shall remain in effect until a postimplementation evaluation report has been approved by the Department of Technology. The Department of Technology shall post a notice on its Internet Web site when the report is approved.
(b) The FISCal Project Office shall report to the Legislature, by February 15 of each year, an update on the project. The report shall include all of the following:
(1) An executive summary and overview of the project's status.
(2) An overview of the project's history.
(3) Significant events of the project within the current reporting period and a projection of events during the next reporting period.
(4) A discussion of mitigation actions being taken by the project for any missed major milestones.
(5) A comparison of actual to budgeted expenditures, and an explanation of variances and any planned corrective actions, including a summary of FISCal project and staffing levels and an estimate of staff participation from partner agencies.
(6) An articulation of expected functionality and qualitative benefits from the project that were achieved during the reporting period and that are expected to be achieved in the subsequent year.
(7) An overview of change management activities and stakeholder engagement in the project, including a summary of departmental participation in the FISCal project.
(8) A discussion of lessons learned and best practices that will be incorporated into future changes in management activities.
(9) A description of any significant software customization, including a justification for why, if any, customization was granted.
(10) Updates on the progress of meeting the project objectives.
(c) The initial report, due February 15, 2013, shall provide a description of the approved project scope. Later reports shall describe any later deviations to the project scope, cost, or schedule.
(d) The initial report shall also provide a summary of the project history from Special Project Report 1 to Special Project Report 4, inclusive.
(e) This section shall remain in effect until a postimplementation evaluation report has been approved by the Department of Technology. The Department of Technology shall post a notice on its Internet Web site when the report is approved.
