PRINCE2 and ITIL alignment
The Programme and Project layer uses PRINCE2 for project control and ITIL for the route into live service, so PMO, assurance and IT service management teams recognise every role, record and decision. DelPulse adds sprints inside stages, safety and compliance, and handover to a product team.
Why align
Many organisations already run projects to PRINCE2 and live services to ITIL. DelPulse uses their structure and names at the Programme and Project layer, so a project can be governed, assured and taken into service without translating between methods.
- PRINCE2: aligned with the 7th edition (2023): principles, roles, processes and management products.
- ITIL: uses the ITIL 4 practice names, which carry forward into ITIL (Version 5), released in stages from 2026.
PRINCE2® and ITIL® are registered trademarks of PeopleCert group. DelPulse is aligned with them and is not affiliated with or endorsed by PeopleCert. Certification and the official guidance come from PeopleCert.
PRINCE2 principles in DelPulse
| Principle | How DelPulse applies it |
|---|---|
| Continued business justification | The business case is approved at G1 and checked at every gate in the end stage report. If it is no longer justified, the Project Board stops or re-plans the project. |
| Learn from experience | Lessons are logged in every stage, reviewed at the Lessons Learned Review and fed into the improvement backlog and the next project. |
| Defined roles, responsibilities and relationships | Every project has a Project Board (SRO as Executive, Senior User, Senior Supplier), a Project Manager, Project Assurance and Project Support. DelPulse adds the Receiving Product Manager. |
| Manage by stages | The eight lifecycle phases are management stages, separated by gates G0 to G5. Within a stage, teams deliver in two-week sprints. |
| Manage by exception | Tolerances for time, cost, scope, quality, benefits, risk and sustainability are set in the charter. A forecast breach goes to the board as an exception report. |
| Focus on products | Every artifact is a defined product with an owner, a template and approvers. The project product is described in the brief and accepted at handover. |
| Tailor to suit the project | Default rules can be tailored in the project charter, and the reason is recorded. Safety and compliance criteria are never removed. |
What DelPulse adds
- Sprints inside stages, with the same team events and Definition of Done as product teams.
- A Receiving Product Manager named at G1, and accepted handover, not go-live, as the end of the project.
- Safety and compliance as a hard criterion at go-live and handover.
- The DelPulse Value Index for deferred items moving to the product backlog.
- Rules enforced in the governance workspace: gates cannot pass without their criteria.
The rest of this page is for subscribers
Subscribe to read the other 7 sections of this page:
- PRINCE2 processes, phases and gates
- Roles
- Management products and DelPulse artifacts
- Tolerances and management by exception
- ITIL practices along the lifecycle
- The route into live service
- In the governance workspace