TPM Command Center — as of 2026-08-14
The Aug 14 status check rates the project **RED**: the critical path has already slipped one business day, moving the finish from 2026-08-20 to 2026-08-21. The independent Monte Carlo forecast corroborates that exact date at the 50th percentile — two different methods, the same number — but it also localizes the residual risk more precisely than the status report alone does: Platform Eng, the team whose task started the slip, is now forecast comfortably **on track** on its own remaining work, while the real tail risk sits with **Backend Eng**, whose most recent sprint came in well under its trailing average. Their 95th-percentile forecast finish, 2026-08-24, is three days later than the status report's revised date — the number worth watching isn't the one already in the RAG report, it's this one.
| Epic | Priority | Tasks | Points |
|---|---|---|---|
| EPIC-1 — Multi-currency expense submission & display | High | 8 | 28 |
| EPIC-2 — Shared approval-resolution engine & delegate setup | High | 5 | 22 |
| EPIC-3 — Delegate notifications & audit trail | Medium | 4 | 13 |
| EPIC-4 — Admin controls for rollout | Medium | 3 | 7 |
| EPIC-5 — Finance reporting export updates | Medium | 3 | 8 |
Planned finish: 2026-08-20
| Task | Team | Start | Finish |
|---|---|---|---|
| EPIC-2-1 — Build shared approval-resolution service for normal and delegate routing | Platform Eng | 2026-08-03 | 2026-08-11 |
| EPIC-2-3 — Store delegation records with auto-expiry at end of date range | Backend Eng | 2026-08-11 | 2026-08-14 |
| EPIC-3-4 — Extend notification service for delegation lifecycle events | Platform Eng | 2026-08-14 | 2026-08-20 |
The critical path has already slipped: EPIC-2-1 (zero slack) finished one business day late on Aug 12, and EPIC-2-3 (also zero slack) is now confirmed one day behind as a result, with Backend Eng stating there's no way to compress it further. Absent a decision to compress EPIC-3-4, the project finish moves from 2026-08-20 to 2026-08-21. Overall status reflects this — the worst-rated load-bearing epic — even though the slip is one day and one open risk (the compliance question on export attribution) was resolved this period.
| Severity | Risk | Owner | Ask |
|---|---|---|---|
| HIGH | Critical path has slipped 1 business day (EPIC-2-1 → EPIC-2-3), with no compression available on the Backend Eng side. | Platform Eng / Backend Eng | Confirm whether to accept the 1-day slip to 2026-08-21, or authorize parallel/expedited work on EPIC-3-4 to try to hold the original 2026-08-20 date. |
| MEDIUM | FX integration (EPIC-1-2) burned half its schedule buffer resolving a vendor rate-limit issue; only 1 day of slack remains if it recurs. | Backend Eng | No action needed yet — flagging so it isn't a surprise if this needs escalation next period. |
| MEDIUM | EPIC-3-4 hasn't started and the whole revised finish date depends on its 4-day estimate holding exactly, with zero slack to absorb any further surprise. | Platform Eng | None currently — monitoring. Will escalate if EPIC-2-3 slips past Aug 15. |
Planned finish 2026-08-20 — P50 2026-08-21, P85 2026-08-21, P95 2026-08-24.
| Team | Remaining pts | P50 | P85 | P95 | Risk | Load-bearing |
|---|---|---|---|---|---|---|
| Backend Eng | 13 | 2026-08-21 | 2026-08-21 | 2026-08-24 | LIKELY LATE | Yes |
| Platform Eng | 5 | 2026-08-19 | 2026-08-19 | 2026-08-19 | ON TRACK | Yes |
| Finance Eng | 3 | 2026-08-18 | 2026-08-18 | 2026-08-18 | ON TRACK | No |
| Web Eng | 8 | 2026-08-19 | 2026-08-19 | 2026-08-19 | ON TRACK | No |
| Mobile Eng | 0 | 2026-08-14 | 2026-08-14 | 2026-08-14 | ON TRACK | No |