Service life and health
How a service is doing from go-live, through early life support and stabilisation, into everyday running: incidents a day, open P1 and P2, the share fixed within the service level, availability, time to fix, satisfaction and open problems, week by week. The project’s exit criteria fill from the same figures, and the product’s benefits sit alongside.
Why it matters
A project is judged at go-live, but a service is judged in the weeks after. Following the same figures from early life support to everyday running shows whether the change succeeded and when it is safe to hand over.
- Owner
- Service Owner
Draws on
Led or owned by
In the resource library
Ready-to-use resources in the DelPulse workspace (sign in to open them):
- Service Owner self-assessment · Self-assessments
The rest of this page is for subscribers
Subscribe to read the other 4 sections of this page:
- How to run it
- Rules
- In the DelPulse workspace
- If you use Jira or Azure DevOps