The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win

Content Warning: This section of the guide includes discussion of bullying and gender and transgender discrimination.

Palmer has to leave the budget meeting early due to a purchasing outage. At the NOC, everyone denies responsibility for the error. When McKee reaches out to Pesche to check firewalls, Brent says he might have fixed it. Though Palmer tells Brent to discuss actions with him before making them, the team congratulates Brent for resolving the issue. Palmer chastises McKee and Davis for the disorganized way they handle emergencies, adding that he suspects Brent both caused and fixed the problem.

At the Wednesday CAB meeting, Palmer is pleased to find that everyone who needed to come is there. Attendees organize the proposed changes by risk, reviewing and approving the highest-risk changes. McKee notes that over 100 changes are scheduled for Friday, when Phoenix releases. People reschedule their changes to avoid conflicts as Palmer revisits his conversation with Reid. At the end of the meeting, everyone is happy, and Davis congratulates McKee on her work. Afterward, Palmer realizes that changes are another form of work. He now knows three of the four types of work: business projects, internal IT Operations projects, and changes.