Loading your book clubs
There was a problem loading your book clubs. Please try again.
Not in a club? Learn more
Join or create book clubs
Choose books together
Track your books
Bring your club to Amazon Book Clubs, start a new book club and invite your friends to join, or find a club that’s right for you for free.
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required. Learn more
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Flip to back Flip to front
| Price | New from | Used from |
|
Audible Audiobook, Unabridged
"Please retry" |
$0.00
| Free with your Audible trial | |
- Read with Our Free App
-
Audiobook
$0.00 - 74 Used from $2.45 12 New from $29.99 2 Collectible from $14.99
Great on Kindle
Great Experience. Great Value.
Putting our best book forward
Each Great on Kindle book offers a great reading experience, at a better value than print to keep your wallet happy.
Explore your book, then jump right back to where you left off with Page Flip.
View high quality images that let you zoom in to take a closer look.
Enjoy features only possible in digital – start reading right away, carry your library with you, adjust the font, create shareable notes and highlights, and more.
Discover additional details about the events, people, and places in your book, with Wikipedia integration.
Get the free Kindle app: 
Enjoy a great reading experience when you buy the Kindle edition of this book.
Learn more about Great on Kindle, available in select categories.
There is a newer edition of this item:
Frequently bought together
- +
- +
Total price:
To see our price, add these items to your cart.
Choose items to buy together.
What do customers buy after viewing this item?
Page 1 of 1 Start overPage 1 of 1
From the Publisher
|
|
|
|
|
|---|---|---|---|
|
|
|
|
|
The Three Ways of DevOps
|
|
|
|
|---|---|---|
|
The First Way of DevOps emphasizes the performance of the entire system, not a specific silo or department. The focus is placed on all business value streams that are enabled by IT. It begins when requirements are identified (the business or IT), are built (Development), and then transitioned into production (Operations). |
The Second Way of DevOps creates right-to-left feedback loops. The goal is to shorten and amplify feedback loops so that necessary corrections can be continually made. The Second Way facilitates understanding and responding to all customers, internal and external, and embedding knowledge where it is needed. |
The Third Way of DevOps encourages the creations of a culture that fosters continual experimentation (taking risks and learning from failure) and understanding that repetition and practice is the prerequisite to mastery. Practicing the Third Way of DevOps allocates time for the improvement of daily work, creates rituals that reward the team for taking risks, and introduces faults into the system to increase resilience. |
|
|
|
|
|
|---|---|---|---|
Gene KimGene Kim is a multiple award-winning CTO, researcher and bestselling author, and has been studying high-performing technology organizations since 1999. He was founder and CTO of Tripwire for 13 years. He has written six books, including The Unicorn Project (2019), The Phoenix Project (2013), The DevOps Handbook (2016), the Shingo Publication Award winning Accelerate(2018), and The Visible Ops Handbook(2004-2006) series. Since 2014, he has been the founder and organizer of IT Revolution and the DevOps Enterprise Summit, studying the technology transformations of large, complex organizations. |
Jez HumbleJez Humble is co-author of several books on software including Shingo Publication Award winner Accelerate, Jolt Award winner Continuous Delivery, and The DevOps Handbook. He has spent his career tinkering with code, infrastructure, and product development in companies of varying sizes across three continents. He works for Google Cloud as a technology advocate and teaches at UC Berkeley. |
Patrick DeboisPatrick Debois is the Director of DevOps Relations and Advisor at Snyk. In 2009 he coined the word DevOps by organizing the first devopsdays event, as is now often known as one of the grandfathers of DevOps. He organized conferences all over the world to collect and spread new ideas. |
John WillisJohn Willis is Senior Director of the Global Transformation Office at Red Hat. Prior to Red Hat, he was the Director of Ecosystem Development for Docker. John was one of the earliest cloud evangelists and is considered one of the founders of the DevOps movement. John is the author of 7 IBM Redbooks, as well as co-author of the The DevOps Handbook and Beyond the Phoenix Project. |
Shold be NoOps handbook not DevOps
Reviewed in the United States on December 16, 2016
I'm finding this book mostly small minded and hype for the DORA group.The first book "The Phoenix Project" was great and did a good job showing how the silos in tech companies can work together. I was hoping this book would go either deeper in the tech tools and show how to build workflow or more employee management (culture) to bring Sales, Ops and Dev together. Instead this book self conflicting and shallow.Example: "Myth - DevOpst Means Eliminating IT Operations or ""NoOps""". Then says.. "... the right culture norms, small teams of developer are able to quickly, safely, and independently deploy ... changes into production" That is the definition of NoOps.It also talks about building a trusting work place where Devs are allowed to make mistakes (because they can recover from them fast) but says nothing about the human aspect of managers firing Ops people because they missed a 2am alert and it escalated to his boss.It is also written with many absolute comments (sales talk) Like: in chapter 1 when FOCUS(ing) ON DEPLOYMENT LEAD TIME it implies all large batch work can be reduced. This ignores IT issues like conversion of big production data sets that can take weeks.This book comes with an code to "TAKE THE DORA DEVELOP X-RAY ASSESSMENT AND SEE WHERE YOU STAND". Marc Andreessen is famously quoted as saying, "The spread of computers and the internet will put jobs in two categories: people who tell computers what to do, and people who are told by computers what to do." Or, "automate all the things" and reduce work and work force. The Answer is - Get out of OPS go back to DEV and prepare to work on small meaningless bit of code.The one subject this book does cover that the Phoenix Project did not is SECURITY. However, this books still see the Sec group as outsiders writing tasks (after the fact), reviewing Dev code and training DevOps and creating DevOpsSec. It thinks or hopes security problems can be coded away with tools like Gauntlt.Conclusion: If you're looking for some good quotes about why / how you / 're company should / can move faster to build a minimum viable product (MVP) in the lease amount of time by WIP-ing works not creating it.... This book is for you.
Reviewed in the United States on December 16, 2016
Images in this review
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Reviewed in the United States 🇺🇸 on January 1, 2018
Reviewed in the United States 🇺🇸 on December 16, 2016
The first book "The Phoenix Project" was great and did a good job showing how the silos in tech companies can work together. I was hoping this book would go either deeper in the tech tools and show how to build workflow or more employee management (culture) to bring Sales, Ops and Dev together. Instead this book self conflicting and shallow.
Example: "Myth - DevOpst Means Eliminating IT Operations or ""NoOps""". Then says.. "... the right culture norms, small teams of developer are able to quickly, safely, and independently deploy ... changes into production" That is the definition of NoOps.
It also talks about building a trusting work place where Devs are allowed to make mistakes (because they can recover from them fast) but says nothing about the human aspect of managers firing Ops people because they missed a 2am alert and it escalated to his boss.
It is also written with many absolute comments (sales talk) Like: in chapter 1 when FOCUS(ing) ON DEPLOYMENT LEAD TIME it implies all large batch work can be reduced. This ignores IT issues like conversion of big production data sets that can take weeks.
This book comes with an code to "TAKE THE DORA DEVELOP X-RAY ASSESSMENT AND SEE WHERE YOU STAND". Marc Andreessen is famously quoted as saying, "The spread of computers and the internet will put jobs in two categories: people who tell computers what to do, and people who are told by computers what to do." Or, "automate all the things" and reduce work and work force. The Answer is - Get out of OPS go back to DEV and prepare to work on small meaningless bit of code.
The one subject this book does cover that the Phoenix Project did not is SECURITY. However, this books still see the Sec group as outsiders writing tasks (after the fact), reviewing Dev code and training DevOps and creating DevOpsSec. It thinks or hopes security problems can be coded away with tools like Gauntlt.
Conclusion: If you're looking for some good quotes about why / how you / 're company should / can move faster to build a minimum viable product (MVP) in the lease amount of time by WIP-ing works not creating it.... This book is for you.
Shold be NoOps handbook not DevOps
Reviewed in the United States 🇺🇸 on December 16, 2016
I'm finding this book mostly small minded and hype for the DORA group.Reviewed in the United States 🇺🇸 on December 16, 2016
The first book "The Phoenix Project" was great and did a good job showing how the silos in tech companies can work together. I was hoping this book would go either deeper in the tech tools and show how to build workflow or more employee management (culture) to bring Sales, Ops and Dev together. Instead this book self conflicting and shallow.
Example: "Myth - DevOpst Means Eliminating IT Operations or ""NoOps""". Then says.. "... the right culture norms, small teams of developer are able to quickly, safely, and independently deploy ... changes into production" That is the definition of NoOps.
It also talks about building a trusting work place where Devs are allowed to make mistakes (because they can recover from them fast) but says nothing about the human aspect of managers firing Ops people because they missed a 2am alert and it escalated to his boss.
It is also written with many absolute comments (sales talk) Like: in chapter 1 when FOCUS(ing) ON DEPLOYMENT LEAD TIME it implies all large batch work can be reduced. This ignores IT issues like conversion of big production data sets that can take weeks.
This book comes with an code to "TAKE THE DORA DEVELOP X-RAY ASSESSMENT AND SEE WHERE YOU STAND". Marc Andreessen is famously quoted as saying, "The spread of computers and the internet will put jobs in two categories: people who tell computers what to do, and people who are told by computers what to do." Or, "automate all the things" and reduce work and work force. The Answer is - Get out of OPS go back to DEV and prepare to work on small meaningless bit of code.
The one subject this book does cover that the Phoenix Project did not is SECURITY. However, this books still see the Sec group as outsiders writing tasks (after the fact), reviewing Dev code and training DevOps and creating DevOpsSec. It thinks or hopes security problems can be coded away with tools like Gauntlt.
Conclusion: If you're looking for some good quotes about why / how you / 're company should / can move faster to build a minimum viable product (MVP) in the lease amount of time by WIP-ing works not creating it.... This book is for you.
Images in this review
Reviewed in the United States 🇺🇸 on July 28, 2019
Reviewed in the United States 🇺🇸 on July 17, 2022
Top reviews from other countries
Gavin Deadman
This is the most comprehensive and practical DevOps guide out
Reviewed in the United Kingdom 🇬🇧 on October 7, 2021
Gavin Deadman
Reviewed in the United Kingdom 🇬🇧 on October 7, 2021
It’s quite easy to think that DevOps practices are just something that dev teams deal with and the value is simply just an increase in throughput, but the book provides clarity on the colossal value that adopting a DevOps culture and the principles can have on teams, the business, and customers.
Throughout the book, Gene echoes the importance of having the whole product team (product manager, designer and several engineers)) involved in the transformation, as well as focusing on outcomes, and to achieve outcomes you need to collect data and learn through experimentation which is covered in the book too.
Gene gives good advice that it’s important to avoid funding projects and instead you should fund services and products: “A way to enable high-performing outcomes is to create stable service teams with ongoing funding to execute their own strategy and road map of initiatives”.
This is the most comprehensive and practical DevOps guide out there and the layout makes the content easy to digest. The book covers:
– History leading up to DevOps, and Lean thinking
– Agile, and continuous delivery
– Value streams
– How to design your organisation and architecture
– Integrating security, change management, and compliance
The principles and tech practices of:
1. Flow
2. Feedback
3. Continual Learning and Experimentation
“Our goal is to enable market-oriented outcomes where many small teams can quickly and independently deliver value to the customer”
Images in this review
Deepak
If you're looking for an up to date review this is your book.
Reviewed in the United Kingdom 🇬🇧 on September 3, 2018Amazon Customer
Useful reference and perfect companion to the Phoenix Project
Reviewed in the United Kingdom 🇬🇧 on December 12, 2017JurorNumber8, UK
The best, most digestible and useful work-related book I ever read.
Reviewed in the United Kingdom 🇬🇧 on June 19, 2020
