Delivery health
Delivery watchlist and follow-up
The overview stays quiet. Open the alert list only when you want the details behind warnings or critical issues.
Critical issues need action today. Warnings need a decision, owner, or follow-up this week.
Re-scope work, clear blockers, or move the commitment before the team keeps planning against bad assumptions.
Confirm ownership, adjust timing, or plan explicit follow-up so a warning does not quietly become a blocker.
Alerts cover sprint capacity, release readiness, meeting follow-up, and absence pressure without flooding the overview itself.
Chronological table
Planning timeline
| Date | Type | Title | Project | Meta |
|---|---|---|---|---|
| Mar 30, 2026 00:00 | Sprint | Platform Reliability Sprint | Client Delivery Hub | 0 burned / 55 planned · 98 capacity |
| Mar 30, 2026 09:30 | Meeting | Sprint planning | Client Delivery Hub | Sprint Planning |
| Apr 7, 2026 00:00 | Absence | Lena (Spring break) | — | Full day · Spring break |
| Apr 11, 2026 14:00 | Meeting | Release readiness review | Client Delivery Hub | Release Readiness |
| Apr 13, 2026 00:00 | Release | Platform Stability Release | Client Delivery Hub | Next: QA signed off |
| Apr 14, 2026 00:00 | Absence | Noah (Client visit) | — | Full day · Client visit |