Critical-path risk95% confidence
The critical path runs through 6 activities with no float
Every day lost on this chain is a day lost at launch. No other activity has three weeks of float or less.
PRJ-2026-009At risk4ExecutionHybridIn progressDelivered by:Ministry of Communications and Information Technology
Government Cloud & Ministry Systems Migration
Add to watchlistBuilding the government cloud in the government data centre and moving the ministries’ systems and websites onto it in waves, retiring scattered servers.
Project managerEng. George HaddadProject sponsorEng. Khaled Al-KayyaliProgrammeDigital Infrastructure & Cybersecurity Programme
Budget (BAC)
SYP 1.3B
Actual cost
SYP 629.9M
48% of budget
Progress
47%Awaiting acceptance 12%
Estimate at completion
SYP 1.3B
+SYP 40.2M
SPI · CPI
0.89Schedule performance index · 0.890.97Cost performance index · 0.97
Forecast finish
2027-03-21
21 days behind baseline
ExecutionStage 4 of 5
Next gate:Closure8 January 2027
- Pre-start · CompletePre-start · Complete
- Gate into «Initiation»DecisionGoDate2 April 2025Initiation · CompleteInitiation · Complete
- Gate into «Planning»DecisionConditional goDate1 June 2025Planning · CompletePlanning · Complete
- Gate into «Execution»DecisionGoDate11 September 2025Execution · Current stageExecution · Current stage
- Gate into «Closure»DecisionNot held yetDate8 January 2027Closure · Not startedClosure · Not started
Schedule & Gantt
The plan with its planned, actual and forecast dates, baselines, links and critical path. The forecast is scheduled from the data date through the links and constraints.
Finish-date drift
+18 days vs approved
Baseline (original = approved)2027-02-28
Current forecast2027-03-18
By earned schedule2028-05-10
- Critical activities
- 7
- of 9 open activities
- Late activities
- 6
- past their baseline finish
- Schedule performance
- 0.52
- earned ÷ planned value
- Next milestone
- in 53 days
- Build complete
Layers
Compare with
ActivityOwnerForecast finishProgress
2027-03-1847%
Government Cloud & Ministry Systems MigrationPlanned: 2025-06-01 → 2027-02-28Forecast: 2025-06-01 → 2027-03-18Float: 0d
2026-01-25100%
Management & governancePlanned: 2025-06-01 → 2025-10-22Actual: 2025-06-01 → 2026-01-25
2025-10-26100%
Project plan & baselinePlanned: 2025-06-01 → 2025-08-28Actual: 2025-06-01 → 2025-10-26
2026-01-25100%
Monitoring & reportingPlanned: 2025-07-26 → 2025-10-22Actual: 2025-09-01 → 2026-01-25
2026-01-25100%
Project plan approvedPlanned: 2025-10-22 → 2025-10-22Actual: 2026-01-25 → 2026-01-25Project plan approved
2026-07-28100%
Analysis & designPlanned: 2025-09-19 → 2026-02-09Actual: 2025-12-01 → 2026-07-28
2026-04-27100%
Business requirementsPlanned: 2025-09-19 → 2025-12-16Actual: 2025-12-01 → 2026-04-27
2026-07-28100%
Solution designPlanned: 2025-11-13 → 2026-02-09Actual: 2026-03-03 → 2026-07-28
2026-07-28100%
Designs approvedPlanned: 2026-02-09 → 2026-02-09Actual: 2026-07-28 → 2026-07-28Designs approved
2026-12-2055%
BuildPlanned: 2026-01-07 → 2026-07-23Forecast: 2026-03-03 → 2026-12-20Float: 0d
2026-10-27100%
Release 1Planned: 2026-01-07 → 2026-04-05Actual: 2026-06-03 → 2026-10-27
2026-11-2865%
Release 2Planned: 2026-03-03 → 2026-05-29Forecast: 2026-03-03 → 2026-11-28Float: 0dDrag to change its duration+183
2026-12-200%
IntegrationsPlanned: 2026-04-26 → 2026-07-23Forecast: 2026-11-14 → 2026-12-20Float: 0dDrag to change its dates+150
2026-12-200%
Build completePlanned: 2026-07-23 → 2026-07-23Forecast: 2026-12-20 → 2026-12-20Float: 88dDrag to change its datesBuild complete
2027-02-020%
Testing & acceptancePlanned: 2026-06-20 → 2026-11-10Forecast: 2026-12-06 → 2027-02-02Float: 0d
2027-01-110%
System testingPlanned: 2026-06-20 → 2026-09-16Forecast: 2026-12-06 → 2027-01-11Float: 0dDrag to change its dates+117
2027-02-020%
User acceptance testingPlanned: 2026-08-14 → 2026-11-10Forecast: 2026-12-28 → 2027-02-02Float: 0dDrag to change its dates+84
2027-02-020%
Testing & acceptance completePlanned: 2026-11-10 → 2026-11-10Forecast: 2027-02-02 → 2027-02-02Float: 44dDrag to change its datesTesting & acceptance complete
2027-03-180%
Launch & handoverPlanned: 2026-10-08 → 2027-02-28Forecast: 2027-01-19 → 2027-03-18Float: 0d
2027-02-240%
Training & changePlanned: 2026-10-08 → 2027-01-04Forecast: 2027-01-19 → 2027-02-24Float: 0dDrag to change its dates+51
2027-03-180%
Go-live & handoverPlanned: 2026-12-02 → 2027-02-28Forecast: 2027-02-10 → 2027-03-18Float: 0dDrag to change its dates+18
2027-03-180%
Final handoverPlanned: 2027-02-28 → 2027-02-28Forecast: 2027-03-18 → 2027-03-18Float: 0dDrag to change its datesFinal handover
- Activities (forecast)
- Baseline
- Slip past baseline
- Critical
- Milestone
- Phase / element
- Today
22 rows shown · Data date 2026-10-28
AI schedule analysis
Computed from the current plan: 9 open activities, data date 2026-10-28
Unrealistic durations78% confidence
“Release 2” needs a pace 4.2× faster than it has kept
It earned 65% in 239 days; the forecast assumes the rest in 31 days. At the pace so far it finishes on 2027-03-06.
Slippage pattern84% confidence
Milestones slip 125 days on average
Each milestone’s slip in days, in date order; the later ones slip more than the early ones.
95
169
150
84
G1G2G3G4
The critical chain
In date order, to final acceptance