Start and Scaling Devops in the Enterprise

by Gary Gruver, Jez Humble (Foreword)

DevOps is a fundamental shift in how leading edge companies are starting to manage their software and IT work. Businesses need to move more quickly than ever before, and large software organizations are applying these DevOps principles to develop new software faster than anyone previously thought possible. DevOps started in small organizations and in large organizations that had or created architectures that enabled small teams to independently develop, qualify, and deploy code. The impact on productivity is so dramatic that larger organizations with tightly coupled architectures are realizing they either need to embrace DevOps or be left behind. The biggest challenge is that they can’t just empower small teams to work independently because their legacy architectures require coordinating the development, qualification, and deployment of code across hundreds of people. They need a DevOps approach that not only addresses their unique challenges, but also helps them reach an organization-wide agreement on where to start and how to scale DevOps. That is where Starting and Scaling DevOps in the Enterprise comes in. Starting and Scaling DevOps in the Enterprise is a quick, easy-to-read guide that helps structure those improvements by providing a framework that large organizations can use to understand DevOps principles in the context of their current development processes and gain alignment across the organization for successful implementations. The book illustrates how to analyze your current development and delivery processes to ensure you gain positive momentum by implementing the DevOps practices that will have the greatest immediate impact on the productivity of your organization, with the goal of achieving continuous improvement over time.

94 pages, Kindle Edition

Published October 27, 2016

Reviews

[Eric Hopkins · Rating 3 out of 5]

A short review of transitioning to a team or teams towards devops, automation, CI/CD, etc. It focuses mostly on larger enterprises and particularly on "peopleware" kind of problems.

The book makes a compelling case for for why devops is good, but struggles to suggest much in the way of actionable ideas because of how varied enterprise development teams can be.

The book would be helpful if you're trying to put together an argument for why your team needs to start doing devops. But will likely leave you wanting more while trying to come up with a plan of action to implement it.

[Berat Onur Ersen · Rating 4 out of 5]

A very useful read for people searching for ideas and recommendations to apply in big corporates.
Importance of deployment pipeline, automation, things like how to approach loosely and tightly coupled systems while searching for efficiency are very well explained.

The best thing about this book was;
examples, applicable methods in the book do not stand as de-facto standards, you have to find your own way to implement. You can get each idea as is, or you can find your own way by getting inspired.

In a nutshell, a very well structed read for leaders, executives and devops enthusiasts.

[Luis Peris · Rating 2 out of 5]

The book is a good summary of some scenearios and is focused on making clear that different practices are better suited for specific situations. Moreover it facilitates a list of questions to evaluate the state of your development process. However, the advice is trivial and does not go deep into any aspect. If you are knowledgeable about continuous delivery, you know what is the value stream mapping technique and the Kanban method this book does not add anything important.

[David Carpinteiro · Rating 4 out of 5]

A good book on devops methodology. Follows a series of stage divided in chapters, on how to move from nothing into a full devops operations in companies. Presents issues and difficulties that will arise during the implementation and how to deal with them.
Only problem, it's a very small book, lacking the practical part.

[Visvaldas · Rating 4 out of 5]

Has chapters with key concepts summarized. good enough and convenient to re-cap of what was the chapter about