Maturity Model · 01 of 3
The Levels
What each level looks like, how a score is made, and why it is a staircase.
AssessEvaluateAgree the targetPlan the gapRe-scoreScore → target
01
What Each Level Looks Like
Signals an assessor looks for, area by area.
| Area | 01 · Initiate | 02 · Challenger | 03 · Mastery |
|---|---|---|---|
| Process | Ad hoc, depends on individuals | Repeatable across teams | Integrated end to end |
| Automation | Manual or basic tools | Some automation, with CI/CD | Fully automated, self-healing |
| Governance and risk | Limited standardisation | Basic governance and risk management | Aligned with business goals |
| Visibility | Little measurement | Dashboards and reporting | Measurable everywhere |
| Adoption | Awareness of why it matters | Established in teams | Organisation-wide |
02
How a Score Is Made
1 of 5
Assess
Current state, from interviews, documents and tool access.
03
Why Not Jump Straight to Mastery?
Lessons NGT's offerings carry from earlier programmes.
Jump straight to Mastery Climb one level at a time
Scope✕Organisation-wide on day one✓One delivery centre or 2–3 pilot apps first
Platform✕A full portal before anyone uses it✓Thinnest viable platform for the worst friction
Organisation✕A big-bang reorganisation✓Platform teams formed over 6–12 months
Habits✕New tools, old habits✓Each level builds on the routines of the last
SourcesNGT Cloud, DevOps and AI Service Offerings v2.0 (Mar 2025)NGT DevSecOps Service Offering (Jan 2025)Puppet, State of DevOps research (five stages of DevOps evolution)NGT Platform Engineering v1.2 (Sep 2026)NGT DataOps Service Offering drafts (Sep 2026)FPT Software Hanoi AI Service Introduction v0.9.3 (Mar 2026)