More than ever, the effective management of technology is critical for business competitiveness. For decades, technology leaders have struggled to balance agility, reliability, and security. The consequences of failure have never been greater whether it is the healthcare.gov debacle, the Target cardholder data breach, or missing the boat with Big Data in the cloud. And yet, high performers using DevOps principles, such as Google, Amazon, Facebook, Etsy, and Netflix, are routinely deploying code into production hundreds, or even thousands, of times per day, while providing world-class agility, reliability, and security. In contrast, most organizations struggle to do releases every nine months.  By studying over 14,000 IT professionals worldwide, the authors have observed that high-performing organizations are 2.5 times more likely than their peers to exceed profitability, market share, and productivity goals. The DevOps Handbook shows leaders how to replicate these incredible outcomes, describing what is required from all parts of the technology organization. Product Management, Development, Test, IT Operations, and Information Security working together can create the cultural norms and the technical practices necessary to maximize organizational learning, increase employee satisfaction, and win in the marketplace.

Table of Contents:
Preface xi Foreword xix Imagine a World Where Dev and Ops Become DevOps: An Introduction to The DevOps Handbook xxi PART ITHE THREE WAYS 1 Part I Introduction 3 1 Agile, Continuous Delivery, and the Three Ways 7 2 The First Way: The Principles of Flow 15 3 The Second Way: The Principles of Feedback 27 4 The Third Way: The Principles of Continual Learning and Experimentation 37 PART IIWHERE TO START 47 Part II Introduction 49 5 Selecting Which Value Stream to Start With 51 6 Understanding the Work in Our Value Stream, Making it Visible, and Expanding it Across the Organization 61 7 How to Design Our Organization and Architecture with Conway's Law in Mind 77 8 How to Get Great Outcomes by Integrating Operations into the Daily Work of Development 95 PART IIITHE FIRST WAY:THE TECHNICAL PRACTICES OF FLOW 107 Part III Introduction 109 9 Create the Foundations of Our Deployment Pipeline 111 10 Enable Fast and Reliable Automated Testing 123 11 Enable and Practice Continuous Integration 143 12 Automate and Enable Low-Risk Releases 153 13 Architect for Low-Risk Releases 179 PART IVTHE SECOND WAY: THE TECHNICAL PRACTICES OF FEEDBACK 191 Part IV Introduction 193 14 Create Telemetry to Enable Seeing and Solving Problems 195 15 Analyze Telemetry to Better Anticipate Problems and Achieve Goals 215 16 Enable Feedback So Development and Operations Can Safely Deploy Code 227 17 Integrate Hypothesis-Driven Development and A/B Testing into Our Daily Work 241 18 Create Review and Coordination Processes to Increase Quality of Our Current Work 249 PART VTHE THIRD WAY: THE TECHNICAL PRACTICES OF CONTINUAL LEARNING AND EXPERIMENTATION 267 Part V Introduction 269 19 Enable and Inject Learning into Daily Work 271 20 Convert Local Discoveries into Global Improvements 287 21 Reserve Time to Create Organizational Learning and Improvement 299 PART VITHE TECHNICAL PRACTICES OF INTEGRATING INFORMATION SECURITY, CHANGE MANAGEMENT, AND COMPLIANCE 309 Part VI Introduction 311 22 Information Security as Everyone's Job, Every Day 313 23 Protecting the Deployment Pipeline, and Integrating into Change Management and Other Security and Compliance Controls 333 Conclusion to the DevOps Handbook: A Call to Action 347 ADDITIONAL MATERIAL 351 Appendices 353 Additional Resources 366 Endnotes 370 Index 409 Acknowledgments 435 Author Biographies 439