Copyright; Table of Contents; Foreword; Preface; Conventions Used in This Book; O'Reilly Safari; How to Contact Us; Acknowledgments; Chapter 1. Evaluating the Incident Response PROCESS; Summary; Chapter 2. The Incident Management System (IMS); Overview of Incident Command; The Culture of Incident Response; Common Terminology for Job Functions; Summary; Chapter 3. The Incident Commander (IC); Resolving the Incident; Communication Methods; Developing the Incident Action Plan; Size Up the Incident; Triage; Act; Review; It's All About TIME; Tone; Interaction; Management; Engagement; Summary Chapter 4. Scaling the Incident ResponseIncident Response and Escalation; Span of Control; Transfer of Command; Summary; Chapter 5. Unified Command (UC); UC in Action; The UC Planning Wheel; Planning Wheel in Action; UC Org Chart; UC Case Study; Launching UC: The Programmatic Backend; Key UC Positions and Checklists; Summary; Chapter 6. After Action Review (AAR); The Name Is Important; AAR as an Integrated Effort; AAR Documentation and Data Collection; Documenting an Incident: A Case Study; Timeline; Case Study AAR; Training; Accountability; Leadership; Empowerment; Notification; Trust AAR Case Study: The New SMEIssue Identified During the AAR; Change Recommendations from the AAR; Summary; Index; About the Authors

Software development is morphing from traditional monolithic releases built by Waterfall development teams into continuous software delivery using Agile project management. Since developers are continuously in the code base, operations must understand this constantly evolving environment to operate it and repair it when it breaks. This practical book will help you deliver high-performance, high reliability, process-oriented IT Operations.