The phoenix project book summary

7.61  ·  9,241 ratings  ·  890 reviews
Posted on by
the phoenix project book summary

Book Review: The Phoenix Project - Continuous Delivery

This parable of an IT project on the brink of destruction is told with humor and insight. Claire reviews the book, finding that conflict, incidents and mistakes are inevitable - what counts is how the team members grow to manage and resolve them. As often found in novels, there are a number of characters to keep track of. The synopsis is simple. It soon becomes clear that among standard responsibilities, Bill and his team are responsible for making the launch of the risky doomed Project Phoenix a success. Project Phoenix not only seems to be hugely overscoped for its ambitious — and imminent — timelines, but it also faces enormous pressure elsewhere. This is mainly because the future of the company appears to hang almost entirely on Project Phoenix.
File Name: the phoenix project book
Size: 51942 Kb
Published 16.02.2020

The Phoenix Project: Out of the Ashes - Jesse Stewart - TEDxSugarLand


Hm, and story-telling is what allows people to evangelize the concepts across and up the organization, but everybody has his taste i personally very much like Archer's writings, and Parts Unlimited have structure. Studies have repeatedly shown that story-telling is the most effective mode of communications! The book gets a little improbable by the end. By the end of .

The business always demands Brent because he is fast and knows about almost everything. Yeah, the writing is on a level with people like E. Porject details here. Finished it.

Find a DevOps meetup near you. You know how every manager has his the book. Federal Managed Service Providers. Community comments.

Company size:. See more of my reviews at Bettering Me Up. Fictionalising allows you to paint an idealised pictureplausible? He's just not credible as a character.

This pop-up will close itself in a few moments. How important is this. This means that the commitments you gave for the planned work can actually be achieved. Welcome to Reddit, the front page of the internet.

See where you can see some bolk between the work done in the DevOps transformation of Parts Unlimited and your own experience. Faced with the conflict of Project Phoenix requirements against firefighting and competing projects, gloom and despa. Close OK. Like This Article!

The phoenix project Gene Kim, Kevin Behr and George Spafford was in In the book, we get to know and appreciate why DevOps is important.
further up the road bruce springsteen book

Want to add to the discussion?

What is DevOps? Learn about it on our wiki! All articles will require a short submission statement of sentences. Use the article title as the submission title. Do not editorialize the title or add your own commentary to the article title. Follow the rules of reddit.

To see what your friends thought of this book, please sign up. They access the developers directly in order to get things done. Some books you recommend to your colleagues and employees. It's terribly written symmary a fantastic resource. Instead it shows that with genuine collaboration in place everybody can give their best contribution to resolve problems and support the business in an agile and controlled fashion without resorting to the blame game.

Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Other editions. Enlarge cover.


Trivia About The Phoenix Proje It is even getting worse because Brent is so busy with solving problems, he is not documenting his work and is increasing the dependency on his personal expertise. Many of the good ideas of ITSM could have been presented here too.

The key to the company's success in the book wasn't automation or continuous delivery. Goodreads is hiring? Especially managing, the key that unlocks advancement to New Ways. Company role:.

So I don't think you have to read it unless you want "relaxing" reading about DevOps domain. Company size:. I wish I could write this well? View the discussion thread!

I am not stating here that old processes or tooling are bad by default. Related Vendor Content? It's like a garbage man writing a book where the garbage man is the only one who can save the day! Imagine my surprise when I was completely sucked into Bill's world.

2 thoughts on “Book Review: The Phoenix Project - Simple Talk

  1. I am not stating here that old processes or tooling are bad by default. James and Jeffrey Archer. As I'm reading the first few chapters, this book summary me of my attitude towards the Agile Manifesto these days - "nobody This is the first book I've read cover-to-cover in an extremely long time. How does he excuse inspecting live data on a machine that craps out at random moments and corrupts it.🤽‍♀️

Leave a Reply