Introduction
The Delivery Playbook is a way to design and deliver software that makes sure customer value is identified, protected, and realized throughout delivery. No customer misunderstandings or disappointments.
If you haven’t read it, the introduction explains why every team needs a playbook — and the Delivery Playbook has been proven with hundreds of companies. It will raise your team’s and your organization’s abilities dramatically. Most importantly, it will enable you to delight your customers.
If you use the referral button below, you’ll earn free premium access to Customer Obsessed Engineering. Just three referrals will earn a free month!
What to bookmark
The Delivery Playbook offers a lot of resources. Finding your way can be a little intimidating at first. Here are a few bookmarks to get you started:
Everything you need to know is a complete table of contents
The index, a more detailed catalogue of content (this page)
The “subway map”
You’ll likely want to bookmark the subway map as well. It provides a visual map of the entire Delivery Playbook, it’s four phases, and their respective 28 activities.
Using the playbook
If you’re new to the Delivery Playbook, start by reading 12 reason to level up your team with a delivery playbook, an introduction to the playbook. From there, I’d recommend reading through each chapter more-or-less in sequence.
If you’ve been using the playbook for a while now, you’ll likely want to treat the following chapters as reference material. I strongly recommend making it “required reading” for your entire team, so everyone is on the same page. You’ll find the subway map an excellent reminder of flow, and each chapter will give you the context you need during delivery.
FREE PREVIEW: If you aren’t a subscriber, check out chapter 2.2 Roadmaps & OKRs. The playbook has over 32 full chapters, plus supporting articles, project templates, and references!
Chapter Index
The playbook is divided into six chapters: An Introduction, four chapters about the playbook phases, Mobilization, Blueprinting, Delivery, and Operations, and a References chapter. The four playbook chapters have numbered sections for easy reference. A glossary of terms is in the References chapter.
Introduction
If you’re new to the Delivery Playbook, start here. These chapters provide an important foundation in core concepts.
Mobilization
Activities conducted in the run-up to a project, such as team selection, onboarding, kickoff calls, and problem space analysis.
Blueprinting
Implementation of overarching architectural designs, and establishing a target state architecture.
Delivery
Creating detailed technical specifications, engineering work, and building a product increment that is ready for production.
Operations
Ensuring security and compliance is “fit-for-purpose,” delivering a product increment, and capturing feedback into the design process of future increments.
References
Publication details
I have questions…
I’d be delighted to talk with you and answer them! Please feel welcome to join the Customer Obsessed Engineering chat here on Substack. I’ll usually get back to you within a business day.
Can I reproduce the Delivery Playbook?
The Customer Obsessed Playbook and web site are copyright © 2011-2024, Boss Logic LLC, all rights reserved. Unauthorized reproduction is prohibited. Organizations interested in reproducing or adapting the Playbook can contact Boss Logic directly.
Can my organization get the complete Delivery Playbook?
Yes, absolutely! Check out the colophon for details on different options available to your organization.
Can I expense my subscription?
You bet! I think that’s a great idea. If you need a starting point, try reaching out to your manager with this template.
And by the way, there are fantastic group discounts. Maybe your company wants to sponsor your whole team?
To learn more about programs for your organization, check out the colophon.
If you find Customer Obsessed Engineering and the Playbook valuable, please share it with your friends and coworkers.