Characters and Roles
DevOps Principles
Automation and Bottlenecks
The Theory of Constraints
Key Tools and Methods
100

This character is the most critical bottleneck in the company’s IT operations, constantly pulled in multiple directions.

Brent

100

This principle encourages the automation of repetitive tasks to save time and reduce human error.

Continuous Integration and Continuous Deployment (CI/CD)

100

Automating this process reduces Brent’s time spent on repetitive, manual tasks.

What is deployment or testing?

100

a methodology for improving processes that focuses on identifying and correcting constraints or root causes of bottlenecks

theory of constraints

100

Bill and his team use this visual method to track work progress and identify bottlenecks.

Kanban

200

Bill works closely with this executive to show how IT improvements have measurable financial benefits. 

Chris

200

Visualizing work to manage WIP and bottlenecks is done using this tool.

Kanban

200

Brent is often referred to as this, a key concept in the Theory of Constraints.

What is a bottleneck?

200

The Theory of Constraints tells us to focus on improving this, which limits the overall performance of a system.

constraint or bottleneck

200

This management principle is introduced to limit the number of tasks being worked on at any one time.

 work-in-process (WIP) limit

300

This character is a key figure in leading the team toward implementing DevOps principles.

Bill Palmer

300

This DevOps principle focuses on increasing feedback loops to catch errors early.

amplifying feedback loops

300

The automation of this task enabled Bill’s team to complete deployments in hours instead of weeks.

What is testing or code deployment?

300

Bill’s team learns that limiting this, the amount of work being handled at once, can improve efficiency.

work-in-process (WIP)

300

A tool that Bill’s team implements to automate testing and deployment.

CI/CD pipeline

400

This executive pressures Bill to deliver results and solve the Phoenix Project's issues quickly.

Steve Masters

400

A key principle of DevOps is to reduce this type of work, which often derails other projects.

unplanned work

400

By automating manual work, Bill’s team aims to reduce this, a major source of delays in IT operations.

What is lead time?

400

One strategy to deal with bottlenecks is to ensure that tasks flow faster through them, reducing this type of work.

multitasking

400

By reducing WIP and automating tasks, Bill’s team dramatically improves this, a key metric for delivering software.

lead time

500

The VP of IT Operations who initially struggles to keep the Phoenix Project on track.

Patty McKee

500

In these chapters, Bill’s team begins creating a culture of continual learning and improvement, embodying this third way of DevOps.

continuous experimentation and learning

500

Uncovering the need for automated testing is key to reducing this kind of error that occurs when humans manually perform tasks.

human error

500

In these chapters, reducing Brent’s workload and automating tasks leads to faster work completion and improves this across the organization.

system throughput

500

The team used Kanban to visualize and manage their work, allowing them to identify these, which were slowing down their processes.

bottlenecks

M
e
n
u