ITIL and IT Service Management for Project Managers: Handing Over to Operations
When a project goes live, it stops being the project team’s responsibility and becomes the support team’s. How smooth that handover is determines whether users experience a well-run service or a stream of unresolved problems. Most IT operations teams organise their work using IT service management (ITSM) practices, and the best known framework is ITIL. Project managers do not need to be ITIL experts, but they do need to speak the language of operations, meet its entry requirements and plan the handover properly.
What Are ITSM and ITIL?
IT service management is the way an organisation designs, delivers, supports and improves the IT services its users depend on. ITIL (originally the Information Technology Infrastructure Library) is a widely used set of good practices for ITSM. The current version, ITIL 4, was introduced in 2019. It is a framework to adapt, not a rulebook, and many organisations also use related approaches such as DevOps and site reliability engineering. Always check which practices your organisation actually uses.
Projects vs Services
| Project view | Service view |
|---|---|
| Temporary effort with an end date | Continuous delivery of value to users |
| Success = deliverables on time and budget | Success = reliable service that meets agreed levels |
| Ends at go-live and closure | Begins at go-live and continues for years |
| Focus on building | Focus on running, supporting and improving |
A project that ignores the service view produces a system that works in testing but cannot be supported in production.
ITIL 4 Key Ideas in Brief
- Service value system: how all components and activities work together to create value.
- Four dimensions: organisations and people, information and technology, partners and suppliers, and value streams and processes. A change should consider all four, not just the technology.
- Guiding principles: for example focus on value, start where you are, progress iteratively with feedback, collaborate, keep it simple and automate where appropriate.
- Service value chain: six activities (plan, improve, engage, design and transition, obtain/build and deliver and support) that turn demand into value.
- Practices: ITIL 4 describes management practices rather than rigid processes.
Practices a Project Manager Will Meet
| Practice | What it does | Why it matters to the project |
|---|---|---|
| Change enablement | Controls changes to production so they are assessed for risk and authorised | Your release into production is a change; plan lead times for approval |
| Release management | Plans and controls moving new or changed services into live use | Aligns your deployment with operations’ calendar and freeze periods |
| Incident management | Restores normal service as quickly as possible after disruption | Support needs a process for issues raised after go-live |
| Service request management | Handles routine user requests such as access or equipment | New services need request types, forms and fulfilment routes |
| Problem management | Finds and removes root causes of recurring incidents | Known errors from testing must be handed over with workarounds |
| Service level management | Defines and monitors agreed service targets | SLAs must be defined before go-live (see Vendor and Procurement Management) |
| Knowledge management | Captures and shares information for users and support staff | Support agents need articles and runbooks before launch |
| Monitoring and event management | Detects and responds to events in the environment | Alerts and dashboards must exist for the new system |
| Service continuity and capacity | Prepares for disruptions and ensures sufficient resources | Disaster recovery and performance planning |
Understanding Change Types
Most organisations categorise production changes so that low-risk work does not queue behind high-risk work:
- Standard change: low risk, well understood and pre-approved, such as a routine access grant.
- Normal change: needs assessment and authorisation, with the level of approval depending on risk. A major project release is usually a normal change.
- Emergency change: needed urgently to fix a major incident, with expedited approval.
Many organisations use a change advisory board or a change authority, and you should learn its schedule and submission deadlines in the planning phase. A go-live date that ignores the change calendar is a schedule risk (see Go-Live, Deployment and Cutover Planning).
Operational Readiness: The Handover Checklist
Operations will not accept a service just because the project says it is finished. Typical entry criteria for service acceptance:
- The service is registered in the service catalogue or configuration database, with owners identified.
- Support model agreed: first-, second- and third-line responsibilities, hours of cover and escalation paths.
- Runbooks and operating procedures written and tested by operations staff.
- Monitoring, alerting and logging configured, with thresholds agreed.
- Backup, restore and disaster recovery tested for the new service.
- SLAs or service targets agreed and measurable.
- Known errors, open defects and workarounds documented.
- Support and operations staff trained, and knowledge articles published.
- Security and access controls reviewed and approved.
- Licences, contracts and vendor support arrangements in place.
- Hypercare period defined, with named project people available (see Change Management and User Adoption in IT Projects).
Agree this checklist with operations early, ideally at planning, and track it like any other deliverable. Operations should be a stakeholder from day one (see Stakeholder Identification and Analysis).
Hypercare and the Move to Business as Usual
Hypercare is a time-limited period, often two to six weeks after go-live, during which the project team provides intensive support alongside operations. It ends against agreed exit criteria, for example no open critical incidents, stable performance and support handling tickets independently. Document the exit decision and have operations formally accept ownership. Then complete project closure (see Project Closure and Lessons Learned).
Worked Example: Handover of an HR Portal
A project manager plans to deliver an HR self-service portal on 1 December. Early in planning, she meets the service desk lead, who shares the entry criteria and the change calendar, which shows a freeze from 20 December. She adds knowledge articles, support training and a monitoring set-up to the plan as deliverables with owners. During testing she discovers that password reset for the portal is not covered by existing service requests, so she asks operations to add a request type. At go-live there are no surprises for the support team, and after a three-week hypercare with declining incident counts, operations signs the acceptance form.
Common Mistakes
- Involving operations only in the last weeks of the project.
- Scheduling go-live without checking change windows and freezes.
- Handing over documentation that operations staff have never tested.
- Leaving SLAs and support hours undefined until after launch.
- Closing the project before hypercare is complete.
- ITIL and ITSM describe how services are run after the project ends; learn the vocabulary.
- Plan for change enablement, release windows, incident handling, SLAs and knowledge articles.
- Agree service acceptance criteria with operations at planning time.
- Use hypercare with clear exit criteria before transferring ownership.