The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win
Rate it:
14%
Flag icon
figuring out what we have time to do and what systems can actually be patched.”
15%
Flag icon
What I need from you is what resources we need.
15%
Flag icon
What does the list look like right now? Where can I get a copy? Who owns the list?”
15%
Flag icon
a lot of the commitments just aren’t written down.”
15%
Flag icon
How can we manage production if we don’t know what the demand, priorities, status of work in process, and resource availability are?
15%
Flag icon
I’m trying to get the list of what all our commitments to the organization are. How big is that list and how do things get on it?”
15%
Flag icon
We can’t make new commitments to other people when we don’t even know what our commitments are now!”
15%
Flag icon
for each of those resources, tell me what their other commitments are that we’re going to be pulling them off of.”
15%
Flag icon
“Make sure you tell people that we’re doing this so we can get more resources. I don’t want anyone thinking that we’re outsourcing or firing anyone,
15%
Flag icon
“You just want a list of organizational commitments for our key resources, with a one-liner on what they’re working on and how long it will take.
15%
Flag icon
which resources are most overutilized and how many new resources we need. That would be the basis of an ask to Steve for more staffing.”
16%
Flag icon
stay focused on the things that matter most to the company.
17%
Flag icon
change controls,
17%
Flag icon
sustainable process that will prevent friendly-fire incidents and get the auditors off our back, while still being able to get work done.
17%
Flag icon
a list of authorized and scheduled changes
17%
Flag icon
“a ‘change’ is any activity that is physical, logical, or virtual to applications, databases, operating systems, networks, or hardware that could impact services being delivered.”
18%
Flag icon
make sure everyone keeps helping us get there. It’s not just to satisfy the audit findings. We need some way to plan, communicate, and make our changes safely.
20%
Flag icon
you don’t release work based on the availability of the first station. Instead, it should be based on the tempo of how quickly the bottleneck resource can consume the work.”
20%
Flag icon
Any improvement made after the bottleneck is useless, because it will always remain starved, waiting for work from the bottleneck. And any improvements made before the bottleneck merely results in more inventory piling up at the bottleneck.”
20%
Flag icon
ensure the fast, predictable, and uninterrupted flow of planned work that delivers value to the business while minimizing the impact and disruption of unplanned work, so you can provide stable, predictable, and secure it service.”
20%
Flag icon
“The First Way helps us understand how to create fast flow of work as it moves from Development into it Operations, because that’s what’s between the business and the customer.
20%
Flag icon
The Second Way shows us how to shorten and amplify feedback loops, so we can fix quality at the source and avoid rework.
20%
Flag icon
Third Way shows us how to create a culture that simul...
This highlight has been truncated due to consecutive passage length restrictions.
20%
Flag icon
experimentation, learning from failure, and understanding that repetition and practice are th...
This highlight has been truncated due to consecutive passage length restrictions.
21%
Flag icon
Either we need to cut down the project list, or we’ve got to staff up.”
21%
Flag icon
You’ve been consistent and clear that Phoenix is the most important, but we can’t seem to keep resources dedicated to it.
22%
Flag icon
“The 80/20 rule likely applies here: Twenty percent of the changes pose eighty percent of the risk.”
22%
Flag icon
We’re predefining high-risk categories of change that not only must have change requests submitted, but must have authorization before being scheduled and implemented.”
23%
Flag icon
people have appropriately informed anyone they could affect, and gotten the ‘okay to proceed’ from all of them.”
23%
Flag icon
the integrity of the process, not so much about the actual changes.”
25%
Flag icon
business projects
25%
Flag icon
internal it projects.
25%
Flag icon
changes
26%
Flag icon
“At the end of each incident, we’ll have one more article in our knowledge base of how to fix a hairy problem and a growing pool of people who can execute the fix.”
27%
Flag icon
When senior engineers get to the level of Brent, or aspire to be Brent, they want to learn and share what they’ve done.
27%
Flag icon
We’ve got to get all this knowledge into the hands of people actually doing the work.
28%
Flag icon
But when was the question ever asked whether we should accept the work? And on what basis did we ever make that decision?
28%
Flag icon
It’s not a good sign when they’re still attaching parts to the space shuttle at liftoff time.
29%
Flag icon
“If you turn the circuit board on and no smoke comes out, it’ll probably work.”
29%
Flag icon
I’m pretty sure we wouldn’t be able to replicate it, because there are too many moving parts.”
30%
Flag icon
lack of competence is the enemy of good.
35%
Flag icon
“It’s not the upfront capital that kills you, it’s the operations and maintenance on the back end.”
36%
Flag icon
business projects, internal projects, and changes.
37%
Flag icon
Maybe what I’m looking for is like dark matter. You can only see it by what it displaces or how it interacts with other matter that we can see.
37%
Flag icon
firefighting.
37%
Flag icon
Unplanned work.
37%
Flag icon
Unplanned work is what prevents you from doing it.
37%
Flag icon
coordinating changes better so they don’t fail, ensuring the orderly handling of incidents and outages to prevent interrupting key resources, doing whatever it takes so that Brent won’t be escalated to…
37%
Flag icon
I tried to take all necessary steps to keep people from doing wrong work, or rather, unplanned work.
37%
Flag icon
‘anti-work,’
« Prev 1 3 4