Project Status Report
A sponsor-facing update showing overall health, deliverable trends, help needed, risks, issues, and decisions that require action.
Public review note: The scenario is educational and sanitized. Names, dates, figures, identifiers, and other details have been changed or generalized for privacy and security.
Overall project status
Overall health: YELLOW
Some risks and issues are present, but the project can remain recoverable if the requirements, schedule, and change request are approved promptly.
| Deliverable | Current health | Forecast / trend | Status detail |
|---|---|---|---|
| Scope | GREEN | YELLOW | The core app scope is defined, but the two new data feeds and updated reporting requirements must be incorporated. |
| Schedule | YELLOW | GREEN | Licensing and activation of the data feeds are estimated at two weeks; the schedule is recoverable if approved promptly. |
| Budget | GREEN | YELLOW | No additional cost has been incurred to date; the proposed change adds a preliminary $2,500. |
Help needed
Must have
Approve the complete, updated app requirements.
Should have
Approve the additional development time and the $2,500 data-feed change.
Like to have
Confirm backup resources for integration, validation, and testing.
Risks and changes since last report
- Version 1 may not include 100% of desired functionality if requirements continue to change.
- Data-feed licensing, activation, or compatibility issues may cause delay or rework.
- Additional scope may create a cost overrun or reduce expected first-year ROI.
- Flu season or other availability constraints could reduce team capacity.
Issues requiring response
- Two additional data-feed sources were identified. Preliminary review indicates an additional $2,500 cost and approximately two weeks for licensing and activation.
- Leadership reporting requirements increased and need confirmation.
Recent and pending decisions
The sponsor must approve the updated requirements, additional data-feed scope, $2,500 budget impact, and schedule impact. The team must also confirm whether an additional sprint or another schedule adjustment is required.
Recognition: Kudos to the team member who identified and helped eliminate a potential customer-facing problem. The technical team should validate licensing, data quality, and integration feasibility before commitment.