Ben is stuck. A development lead with a strong vision for how the intersection of development and operations at his office can be improved, he can't help but feel overwhelmed and discouraged by common problems such as slow turnaround time, rushed and ineffective handover documentation, mounting technical debt, and a lagging QA process. What steps should Ben take to build the momentum needed to create positive changes within his company?
In this unique business novel by Dave Harrison and Knox Lively, two DevOps professionals with years of diverse experience in the industry, you follow Ben as he solves work frustrations in order to adopt Agile, DevOps, and microservices architectures for his organization. Achieving DevOps addresses the "Now what?" moment many DevOps professionals face on their journey. The story provides you with the knowledge you need to navigate the internal political waters, build management support, show measurable results, and bring DevOps successfully into your organization. Come away with practical lessons and timeless business concepts. You'll know how to effect change in a company from the bottom up, gain support, and instill a pattern of progressively building on success. Experience Ben's progress vicariously in Achieving DevOps and bridge the gap between inspiration and the implementation of your own DevOps practices.
Who This Book Is For Those serving as change agents who are working to influence and move their organizations toward a DevOps approach to software development and deployment: those working to effect change from the bottom up such as development leads, QA leads, project managers, and individual developers; and IT directors, CTOs, and others at the top of an organization who are being asked to lend their support toward DevOps implementation efforts
I’m fortunate enough to get a copy for review before publication...
I like the book. It doesn’t pitch a recipe, because there isn’t a recipe for DevOps. It’s more like a menu where you pick things that make your team better. Dave does a good job talking through the pitfalls of certain practices (for instance looking at speed first instead of quality). I appreciate how it’s not all rainbows and unicorns. Changing an enterprise is hard work and it comes with pain and toil and this comes through in the book.
Dave also has a huge list of resources that comprise the best currently known methods of DevOps. Just the linking of these references together alone makes the book worthwhile in my opinion.
This book is a nice mix of fiction story telling to illustrate the principles and an actual discussion of practices and principles relevant to DevOps. In that way this book is superior to both the Phoenix project and the unicorn project. I highly recommend this book for beginning and experienced DevOps practitioners.