Independent Project Oversight Report (IPOR) Rating
-
- Satisfactory, no corrective action necessary.
-
- Caution, risks/issues exist. There may be a need for corrective action in the near future.
-
- Escalated for immediate corrective action. There is a significant risk to the health of the project.
-
- Not enough data is available to make a determination about the project health.
-
No Report Available - Indicates that a Report is not available for publishing for the reporting period.
7100-222 EDDNext: Integrated Claims Management System / Integrated Data Management (ICMS/IDM)
The Employment Development Department (EDD) proposes to modernize the EDD’s benefit systems (Unemployment Insurance, Disability Insurance, and Paid Family Leave) by implementing a single, integrated benefit system that provides customers with a consistent, single portal into EDD’s services, and that lowers the cost to maintain via more agile and responsive solution for deployment of enhancements. The CDT and the EDDNext team have jointly determined that the EDDNext modernization BCP contains three non-delegated IT projects: - EDDNext Project (data platform, UI/DI legacy system replacement, OCR solution, et al.) aka as the “core EDDNext Project” - The Shared Portal Enhancement Project (considered to be a “non-core” EDDNext effort). - The Employer Portal Update Project (considered to be a “non-core” EDDNext effort). The EDDNext Project is required to go through all four stages of project approval lifecycle planning with the CDT. The Shared Customer Portal Enhancement is a delegated project. The Employer Portal Update is a candidate for delegation back to the EDD following receipt of corresponding S1BA’s and PDR submissions.
Project Details
| Agency / State Entity | Labor and Workforce Development / Employment Development Department |
|---|---|
| Total Cost | $817,579,560 |
| Last Approved Start Date | 02/02/2026 |
| Last Approved Finish Date | 02/01/2033 |
| Criticality Rating | High |
| IPOR Reporting Period | Overall IPOR Rating |
|---|---|
| 10/01/2026 - 10/31/2026 |
Independent Project Oversight Dashboard
Key Questions
Is the project on track to satisfy the customer's business objectives?Yes
Is the project on track to achieve the objectives in the approved timeframe?Uncertain
Is the project on track to achieve the objectives within the approved budget?Yes
| Project Overall Health | Comments |
|---|---|
| o Schedule & Development: The pace of user story readiness has slowed while required sprint velocity is expected to increase, plus ongoing integration planning presents a risk to the Release 1 go live on March 17, 2028. o Requirements: Requirements burndown remains low at 15.1%, and end-to-end traceability requires further validation. o Resources & Governance: Potential resource contention and insufficient decision-making criteria require continued attention. o Cost: Cost burndown is 13% versus 34% schedule completion; SI Vendor invoice timing limits visibility into actual cost performance |
| Focus Area/Rating | Comments |
|---|---|
| Governance |
Additional governance and change management criteria are required to reduce the risk of uninformed decisions that could cause approval delays and increase project costs. o Updated plan requires clearer decision-making criteria and stakeholder consultation requirements to support informed decisions and reduce potential impacts to project scope, schedule and cost. o The change management process requires specific Change Request documentation requirements to support timely approvals and reduce the risk of schedule delays and increased costs. o The IPO Manager identified decisions requiring clarification of their rationale, potential contractual impacts, and supporting approvals |
| Time Management |
The slower progression of user stories to Ready status may result in insufficient backlog to support planned sprint velocity, potentially delaying development. o Planned sprint velocity of 440–470 story points exceeds the demonstrated high of 187, requiring increased development capacity that may exceed available State resources and affect Release 1 delivery. o Sprint-end story point completion limits visibility into development progress, potentially delaying identification of performance issues. o Partner-level integration scheduling limits visibility into dependencies and critical path activities, increasing the risk of unidentified delays affecting Release 1 milestones. o Inconsistent mapping between schedule tasks and ADO user stories limits integration progress monitoring, potentially delaying identification of development and schedule impacts |
| Cost & Contract Management |
o The Project's 13% cost burn rate reflects low SI Vendor expenditures (2%), with spending expected to increase as future milestones are completed and accepted. o A $3,963 decrease in cumulative IV&V expenditures requires reconciliation to ensure accurate cost reporting. |
| Scope Management |
Requirements progress and traceability gaps present risks to Release 1 delivery. However, the Project Team has acknowledged the observations and initiated corrective actions. o The Project faces risks to Release 1 scope completion because requirements progress is lagging scheduled completion. These conditions may delay identification of scope gaps and affect Release 1 delivery. o Through Sprint 5, only 15.1% of Release 1 requirements were addressed or planned, compared with 28% overall project completion, increasing the risk of incomplete scope at go-live. o Inconsistent interface documentation across the SI Contract, Integration Plan, and Activity Tracker limits verification that integration activities align with approved requirements and scope. |
| Resources |
o Potential resource contention between ICMS and DMS remains a risk pending portfolio-level validation of shared resource availability against the project's updated schedules. o The IPO Manager's observation is that resource contention risk may be resolved in the next reporting period. |
| Quality |
o ADO contains no test cases associated with user stories in Sprints 6–14, raising concerns about testing readiness and quality as sprint execution accelerates. o The Integration Plan lacks clearly defined interface-level responsibilities, increasing the risk of accountability gaps and coordination issues during integration development and testing. |
| Risk And Issues |
o The IPO Manager continues to actively identify, assess, and monitor project risks and issues through the weekly Risk and Issue Management meetings. o In December 2026, the IPO Manager will assess the Project's risk and issue management practices for consistency with the approved Risk and Issue Management Plan and report any significant findings. |
| Transition Readiness |
o Key Release 1 dependencies and technical readiness activities remain unresolved, potentially affecting integration and delivery. o The IPO Manager recommends completing remaining environments and establishing clear readiness milestones in the schedule. |
| Conditions For Approval |
o The IPMS was submitted on June 5, 2026, approximately four weeks after the required May 8, 2026, deadline. |
| Corrective Action |
Comments about Corrective Action Plan Items N/A |
Green
Yellow
Red
Blue