In IT Process development, the minimum viable runbook (MVR) is the runbook with the highest return on valuable information versus time spent creating it. It is a strategy and process directed toward making and implementing runbooks for your IT team. It is an iterative process of idea generation, prototyping, automation, presentation, information capturing, analysis and learning.
1. Your teams are busy. There is little value in carving out time to have a dedicated team member build runbooks, design processes and gather information from previous successes when you have 24×7 operations that need their attention.
2. Incidents are inevitable, outages are unforeseeable, and frustration can quickly become an internal IT cultural norm. Thus, runbooks are important in providing your teams with contextual documents to support their efforts.
We’ve put together a helpful guide to get you started building a Minimum Viable Runbook. Download it below and get started improving your team’s performance!
Incident Management Buyer’s Guide
Learn what modern incident management is and the value it brings to your IT and on-call teams. In the Incident Management Buyer’s Guide, we explore...Download Now
FREE O'REILLY MEDIA REPORT Post-Incident Reviews
Traditional Post-Incident Review (Post-Mortem) techniques don’t work well in modern IT environments. Why? Because DevOps teams require updated met...Download Now
The 2016/17 State Of On-call
Fast recovery is awesome. On-call misery is not. Over 800 professionals shared a comprehensive picture of life on-call. Their on-call experiences ...Download Now