No abstract

The statements and opinions expressed in this book are those of the author and are not necessarily those of CA, Inc. ("CA").ApressOpen Rights: You have the right to copy, use and distribute this Work in its entirety, electronically without modification, for non-commercial purposes only.Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark.The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights.

During the 2016 Formula 1 season, it's not unusual for pit-stops to hover somewhere around the three-second mark. In rare instances, such as for the Williams F1 team at the 2016 European Grand Prix, the feat has amazingly been accomplished in less than two ticks of the clock.Wrap your mind around that idea for a moment. It will likely take you as long to digest the concept, and it certainly took longer to type out this sentence, than the amount of time required for a 15-20 member pit-crew to pounce on a stopping race car, lift it off the ground, swap four wheels and tires, and then drop it down to be sent on its way. Two seconds! 1 Quality Is Everyone's Responsibility Of course, this larger performance represents a complex chain of lesser events, mapped out and practiced relentlessly by highly-paid, full-time professionals-pit-crews whose sole job is to save their teams and drivers precious seconds that could result in a change in position, and in some cases even a victory.

No abstract

Congratulations, you've read this far and are ready to floor the DevOps accelerator. Like a Formula 1 driver in pole-position at the start of a race, you're eager to get the green light and hit the gas. Hopefully, you're part of a team with a winning culture, managing to business outcomes, and building the strategies needed for continuous improvement. But this is no time to be complacent. Like Formula circuits and race day conditions, business changes constantly. Just as the Monaco circuit demands a different race strategy than Monza, DevOps programs must adjust to different circumstances. For a business focused on operational efficiency (doing more of the same, only faster and cheaper), or government agencies with shrinking budgets, Lean aspects of DevOps might take precedence. But if a business is adjusting its operating model (doing the same things, but in radically different ways), agile methods and continuous delivery will come more to the fore. Whatever the case, be prepared for change and never underestimate the importance of strong culture and building and cultivating great teams.