Medium-Term Plan Implementation Tracker (ministries & governorates)
Add to watchlistA system that follows each ministry’s and governorate’s delivery of the 2026–2028 medium-term plan and the steering committee’s recommendations, with progress indicators and delay alerts.
Budget (BAC)
Actual cost
1% of budget
Progress
Estimate at completion
SPI · CPI
Forecast finish
On baseline
InitiationStage 2 of 5
Next gate:Planning6 September 2026
- Pre-start · CompletePre-start · Complete
- Gate into «Initiation»DecisionGoDate8 July 2026Initiation · Current stageInitiation · Current stage
- Gate into «Planning»DecisionNot held yetDate6 September 2026Planning · Not startedPlanning · Not started
- Gate into «Execution»DecisionNot held yetExecution · Not startedExecution · Not started
- Gate into «Closure»DecisionNot held yetClosure · Not startedClosure · Not started
Scope statementRequired at this stage
What the project delivers, what it does not, and when a deliverable counts as accepted.
A system that follows each ministry’s and governorate’s delivery of the 2026–2028 medium-term plan and the steering committee’s recommendations, with progress indicators and delay alerts.
In scope
- A system that follows each ministry’s and governorate’s delivery of the 2026–2028 medium-term plan and the steering committee’s recommendations, with progress indicators and delay alerts.
- Identity checks against the civil registry
- Integration with internal systems
Out of scope
- Operation and maintenance after the warranty period
- Work outside the approved site or system boundary
Acceptance criteria
- Main deliverable — stage 1Meets the approved specification, signed off by the project owner
- Main deliverable — final stageMeets the approved specification, signed off by the project owner
Scope baselineRequired from Planning
Every approved change creates a new baseline
No baseline yet — it is approved at the planning gate.
Requirements registerRequired from Planning
6 requirements of five kinds, with the trace status of each
By type
- Business1
- Functional2
- Technical1
- Regulatory1
- Security1
Fully traced
0%
0/6 · linked to a deliverable, task and test
Test passed
0%
0/6 · test result is a pass
Accepted
0%
0/6 · signed off by the business owner
Display options
| REQ-023-01 | An end-to-end digital journey, no walk-in | Business | Must | Approved | Iman Al-JasemIman Al-JasemDirector General, Medium-Term PlanP-048iman.aljasem@psa.gov.sy | — | |
| REQ-023-02 | Identity checks against the civil registry | Functional | Must | Approved | Razan Al-RifaiRazan Al-RifaiDirector, Data & AIP-027razan.alrifai@psa.gov.sy | — | |
| REQ-023-03 | A user dashboard | Functional | Must | Approved | Iman Al-JasemIman Al-JasemDirector General, Medium-Term PlanP-048iman.aljasem@psa.gov.sy | — | |
| REQ-023-04 | Integration with internal systems | Technical | Could | Approved | Razan Al-RifaiRazan Al-RifaiDirector, Data & AIP-027razan.alrifai@psa.gov.sy | — | |
| REQ-023-05 | WCAG 2.1 accessibility | Regulatory | Should | Approved | Iman Al-JasemIman Al-JasemDirector General, Medium-Term PlanP-048iman.aljasem@psa.gov.sy | — | |
| REQ-023-06 | National cybersecurity controls | Security | Should | Approved | Razan Al-RifaiRazan Al-RifaiDirector, Data & AIP-027razan.alrifai@psa.gov.sy | — |
Traceability matrixRequired from Execution
Requirement → deliverable → task → test → acceptance. 6 requirements have a gap.