PagerDuty Full-Service Ownership Documentation
Full-service ownership means that people take responsibility for supporting the software they deliver, at every stage of the software/service lifecycle. That level of ownership brings development teams much closer to their customers, the business, and the value being delivered. This guide provides a step-by-step process that software delivery operations teams can use to ensure they are able to fully own their services.
Who Is This For?#
This resource is for team members working in any industry that uses software to deliver high-quality experiences for customers. It helps those teams build highly available systems by empowering them to own the entire lifecycle of their code.
What Is Covered?#
What is Full-Service Ownership?#
An introduction to full-service ownership and why teams should adopt this approach.
How full-service ownership fits into digital transformation initiatives and ways for business stakeholders to quickly demonstrate value.
Defining a Service#
A step-by-step set of considerations to use to determine the size, shape, and boundaries of your "services."
Service Ownership Functions#
A set of functional roles and considerations that account for the needs of a team to successfully own the entire lifecycle of a service.
- Service Documentation
- Service Availability
- Production Operations
- Project Management
- Product Ownership
- Senior Leadership
The Lifecycle of a Service#
The various lifecycle stages of a service and management considerations for each phase.
An example escalation policy, to demonstrate building an incident response pattern appropriate for your business needs.
A step-by-step introduction to going on-call for teams that have never been on-call before.
Tips for Getting Started#
Tips for teams getting started: useful for avoiding common pitfalls.
Tips for Scaling#
After early successes, scaling full-service ownership across an organization presents other challenges.
Links to additional reading to help you get started with full-service ownership.
This documentation is provided under the Apache License 2.0. In plain English, that means you can use and modify this documentation and use it both commercially and for private use. However, you must include any original copyright notices and the original LICENSE file.
Whether you are a PagerDuty customer or not, we want you to have the ability to use this documentation internally at your own company. You can view the source code for all of this documentation on our GitHub account; feel free to fork the repository and use it as a base for your own internal documentation.