How the DEVOPS INSTITUTE® DevOps Standard Integrates with the ITIL® Digital Product and Service Lifecycle
A digital product is not finished when code reaches production. Its value depends on what customers can use, how reliably the service performs, how quickly people receive support, and what the organization learns. ITIL’s digital product and service lifecycle gives us a way to manage that complete responsibility. The new DEVOPS INSTITUTE official book, The DevOps Standard, gives teams a connected operating model for engineering, delivering, governing, and improving it.
These models meet in everyday work. ITIL identifies eight interconnected lifecycle activities: discovery, design, acquisition and allocation, building and testing, transition, operation, delivery, and support. The DevOps Standard book identifies the practices and enabling architecture that help teams perform that work with speed, control, and evidence. The lifecycle is not a one-way handoff; feedback can change decisions at any point.
A lifecycle needs an operating model
The DevOps Standard’s Nine Pillars cover Leadership, Collaborative Culture, Design for DevOps, Continuous Integration, Continuous Testing, Elastic Infrastructure, Continuous Delivery and Deployment, Continuous Security, and Continuous Monitoring and Observability. Each pillar combines people, process, and technology practices. Their value comes from working together across the product and service lifecycle.
The four-layer DevOps Blueprint provides an architectural view: Elastic Infrastructure; the CI/CD Pipeline; Application Release Orchestration; and Value Stream Management. Governance and feedback operate across these layers. ITIL establishes the management context for the product and service, while the pillars and Blueprint help turn decisions into repeatable engineering and operational capability. This is a practical correlation between the two models, not a claim that one formally replaces or is contained within the other.
Follow one AI-enabled change
Suppose a product team wants to add an AI-assisted support feature. The lifecycle clarifies what must be managed; the DevOps model shows what practices and evidence should accompany the change. The activities will overlap, and a running service will continue through operation, delivery, and support while new versions are being built.
| DevOps Contribution in the example |
| Establish the user need, intended outcome, risk tolerance, and measure of value. Leadership, collaboration, and Value Stream Management connect demand to an accountable decision. |
| Specify behavior, human escalation, security, reliability, and observability. Design for DevOps and Continuous Security make these properties part of the product design. |
Acquisition and allocation | Select approved model or service dependencies, data access, suppliers, skills, and capacity. Elastic Infrastructure and platform governance make choices supportable and traceable. |
| Integrate the change, record provenance, and test behavior, quality, security, and failure paths. Continuous Integration and Testing produce evidence rather than a build status alone. |
| Classify release risk, confirm readiness, control exposure, and prepare rollback. Continuous Delivery and Deployment and release orchestration use the evidence to move into service. |
| Monitor service health, AI behavior, cost, drift, and security signals. Infrastructure and observability practices support response and recovery. |
| Verify that customers can use the feature and receive the intended benefit. Value stream and experience measures show whether deployment became value. |
| Resolve incidents, answer user needs, and identify recurring failure. Support evidence returns to design, the backlog, tests, and operating controls. |
Feedback makes the relationship useful
The strongest connection between ITIL and DevOps is the return path. Production telemetry, incidents, user experience, security findings, cost, flow, and business outcomes should inform the next discovery and design decisions. In the AI feature example, a support issue might reveal an unsafe answer pattern. The response should extend beyond closing a ticket: revise the behavior, add a regression evaluation, adjust the release control, and verify the result in operation.
This also changes how maturity is assessed. Counting tools or completed releases says little about whether customers receive value safely. Leaders need a balanced view of flow, quality, security, reliability, experience, cost, and learning. The ITIL lifecycle keeps the product and service responsibility visible; the DEVOPS INSTITUTE Operating Model helps produce the evidence needed to improve it.
Where to begin
Choose one active digital product or service. Map a recent change across the eight ITIL activities, including the decisions made after deployment. Identify which DevOps pillars contributed, where the four Blueprint layers carried the work, what evidence was available, and who owned the next decision. Then find the constraint that most limits value, safety, or learning. Improve that connection first and reassess it using operational and customer outcomes.
ITIL and DevOps are strongest when they describe one system of work. The lifecycle keeps attention on the complete product and service experience. The DevOps Standard connects the people, practices, architecture, governance, and feedback needed to make that experience dependable, even as AI increases the pace of change.
About the author
Marc Hornbeek, known as DevOps-the-Gray, is an award-winning engineer, consultant, author, and instructor with five decades of experience in software and systems engineering. He is CEO of Engineering DevOps Consulting and Intelligent-Institute and a Senior Advisor for the DEVOPS INSTITUTE®. Marc specializes in DevOps, DevSecOps, SRE, platform engineering, continuous testing, AI-native delivery, and governance. He has led more than 95 transformations across enterprises, manufacturers, service providers, and government organizations. Marc is an IEEE Outstanding Engineer and IEEE Life Member and has authored several books on secure, reliable, intelligent, and human-centered engineering.
https://www.linkedin.com/in/marchornbeek
Source context: Marc Hornbeek, “Integrating DevOps with the ITIL Digital Product and Service Lifecycle”; ITIL, “The new ITIL product and service lifecycle model: a connected, ecosystem approach”; PeopleCert, ITIL Product (Version 5).
