Demo data. Any changes do not save and are reset on refresh.
Ransomware Resilience
- Organization
- Demo
- Unit
- Not attached
- Site
- London
Agile
Work remaining
21 person-days remainForecast March 19, 2027, 42 days late
Remaining workIdeal pathCurrent forecast
Work completed
27 of 48 person-days complete56% complete, +4 person-days new scope
Completed workTotal scopeBaseline planCurrent forecast
Cumulative flow
PlannedIn progressBlockedComplete
- As of
- In progress
- 1 milestone
- Blocked
- 0 milestones
- Complete
- 7 milestones
Milestone velocity
PlannedCompleted per monthObserved monthly average
- Completed
- 7 milestones
- Planned
- 7 milestones
- Period
- Aug 2026 to Oct 2026
- Average per month
- 2.33 milestones per month
- Latest month
- Oct 2026, 5 milestones
Project drivers
- RR-P2Prepare recovery access and restoration3 of 6 milestones completed1 blocked milestone; 2 critical-path milestones remaining
- RR-P4Reduce, detect, and exercise ransomware risk1 of 6 milestones completed1 blocked milestone; 1 critical-path milestone remaining
- RR-P1Govern ransomware resilience2 of 4 milestones completedNo blockers recorded
- RR-P3Design resilient service boundaries1 of 2 milestones completedNo blockers recorded
Next actions
- RR-P2-M17Test restoration of critical servicesBlocked; Technical prerequisite
- RR-P4-M18Run and review a ransomware exerciseBlocked; External dependency
- USR-01Validate clean-room identity recovery accessCritical path
- RR-P1-M15Operationalize the ransomware response playbookPlanned
Completed milestones
- RR-P1-M02Define critical services and data
- RR-P1-M03Approve recovery priorities and objectives
- RR-P3-M04Design resilient service architecture
- RR-P2-M05Separate daily and privileged administration
- RR-P2-M06Require strong authentication
- RR-P2-M07Define recovery access procedures
- RR-P4-M08Set endpoint detection and isolation coverage
Recommendations
| Actions | ||||||
|---|---|---|---|---|---|---|
| London | Ransomware ResilienceProgram | USD 180M | Resolve “Test restoration of critical services” with Recovery lead. Agree a recovery sequence for the remaining work and confirm achievable milestone dates.Forecast finish 2027-03-19 is 42 days after the target. | Nov 04, 2026 | ||
| London | RR-P02 Prepare recovery access and restorationProject | USD 180M | Resolve the technical dependency, then retest affected work.RR-17 finishes on Feb 26, 2027, 21 days after its Feb 05, 2027 target. | Feb 05, 2027 | ||
| London | RR-P04 Reduce, detect, and exercise ransomware riskProject | USD 180M | Confirm the external owner, commitment, and date.RR-18 finishes on Mar 19, 2027, 42 days after its Feb 05, 2027 target. | Feb 05, 2027 |
- Site
- London
Ransomware ResilienceProgramUSD 180MRecommendation
Resolve “Test restoration of critical services” with Recovery lead. Agree a recovery sequence for the remaining work and confirm achievable milestone dates.Forecast finish 2027-03-19 is 42 days after the target.- Site
- London
RR-P02 Prepare recovery access and restorationProjectUSD 180MRecommendation
Resolve the technical dependency, then retest affected work.RR-17 finishes on Feb 26, 2027, 21 days after its Feb 05, 2027 target.- Site
- London
RR-P04 Reduce, detect, and exercise ransomware riskProjectUSD 180MRecommendation
Confirm the external owner, commitment, and date.RR-18 finishes on Mar 19, 2027, 42 days after its Feb 05, 2027 target.