Team Guide to Software Operability

Team Guide to Software Operability

Matthew Skelton, Rob Thatcher, and Alex Moore
This is a sample of the book's content.Buy on Leanpub

Table of Contents

Team Guide to Software Operability

  • Team Guides for Software
  • Foreword
  • Introduction
    • What is software operability and why should we care?
    • Where can operability techniques be used?
    • How to use this book
    • Terminology:
    • ‘Slow-burner’ organisational changes:
    • What is covered in this book
    • Why we wrote this book
    • Feedback and suggestions
  • 1. What does good operability look like?
  • 2. Core practices for good software operability
  • 3. Use Run Book collaboration to increase operability and prevent operational issues
    • 3.1 Operational aspects are very similar across many software systems
    • 3.2 Use a Run Book template as a common baseline for operational aspects
    • 3.3 Use a Run Book Dialogue Sheet to facilitate discovery and avoid ‘documentation fallacy’
    • 3.4 Assess operability on a regular basis: every sprint, iteration, or week
    • 3.5 Summary
  • 4. Use modern log aggregation for deep operational insights
  • 5. Use Deployment Verification Tests and Endpoint Healthchecks for rapid feedback on environments
  • 6. Use information radiators and dashboards to drive effective behaviour and good psychological responses
  • 7. Make operability part of the software product
  • 8. Appendix
    • 8.1 Adapt your logging techniques to the technology characteristics
    • 8.2 Understand how the complexity of modern distributed systems drives a need for a focus on operability
  • Terminology
  • References and further reading
    • Introduction
    • Chapter 1 - What does good operability look like?
    • Chapter 2 - Core Operability Practices
    • Chapter 3 - Use Run Book collaboration to increase operability and prevent operational issues
    • Chapter 4 - Use modern log aggregation for deep operational and insights
    • Chapter 5 - Use well-defined readiness checks to increase operational confidence
    • Chapter 6 - Use operability as a differentiating aspect of your software
    • Chapter 7 - Use patterns and principles from Team Topologies to inform the approach to operability
    • Appendix
  • Run Book template
    • Service or system overview
    • System characteristics
    • Required resources
    • Security and access control
    • System configuration
    • System backup and restore
    • Monitoring and alerting
    • Operational tasks
    • Maintenance tasks
    • Failover and Recovery procedures
  • About the authors
    • Matthew Skelton
    • Alex Moore
    • Rob Thatcher
  • Conflux Books
  • Notes
Team Guide to Software Operability/overview

Team Guide to Software Operability

course_overview

Learn how a focus on software operability helps to increase system reliability, reduce problems in Production, and reduce total cost of ownership (TCO).

count_chapters
begin_reading
download
p_implied_book_part_name

Team Guide to Software Operability17 chapters

Begin ›
  1. Team Guides for Software

  2. Foreword

  3. Introduction

  4. 1. What does good operability look like?

  5. 2. Core practices for good software operability

  6. 3. Use Run Book collaboration to increase operability and prevent operational issues

  7. 4. Use modern log aggregation for deep operational insights

  8. 5. Use Deployment Verification Tests and Endpoint Healthchecks for rapid feedback on environments

  9. 6. Use information radiators and dashboards to drive effective behaviour and good psychological responses

  10. 7. Make operability part of the software product

  11. 8. Appendix

  12. Terminology

  13. References and further reading

  14. Run Book template

  15. About the authors

  16. Conflux Books

  17. Notes