In the award winning DevOps book, “The Phoenix Project”, the authors tie together the best practices used by successful manufacturing companies and apply them to a fictional IT project. The concepts from the book have been one of the primary drivers for today’s DevOps organizational transformations.
The character “Brent” represents a critical IT resource that knows everything about the project, is the fastest to implement a solution, and generally the most helpful individual in the organization. Unfortunately, Brent’s talents create a significant bottleneck for the organization.
In this presentation we will discuss ways to identify bottlenecks and how we can help organizations realize the true costs these constraints create. IT bottlenecks can often be difficult to identify as they may be hidden in the organization (purposely or ignorantly). Bottlenecks can be created by organizational structures, antiquated procedures, technical debt, lack of personnel training, etc.
We will also review the principles that derive all DevOps patterns known as the “Three Ways”.

1. Continuously find and implement ways to improve delivery
2. Get fast feedback and work from the strong failure signals to ever-weaker failure signals to get advance warning of quality issues.
3. Use efficiencies gained from the first two ways to introduce rapid experiments that create qualitative gains