Kevin Behr Libri

Bill is an IT manager at Parts Unlimited. It's Tuesday morning and on his drive into the office, Bill gets a call from the CEO. The company's new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but the project is massively over budget and very late. The CEO wants Bill to report directly to him and fix the mess in ninety days or else Bill's entire department will be outsourced. With the help of a prospective board member and his mysterious philosophy of The Three Ways, Bill starts to see that IT work has more in common with manufacturing plant work than he ever imagined. With the clock ticking, Bill must organize work flow streamline interdepartmental communications, and effectively serve the other business functions at Parts Unlimited. In a fast-paced and entertaining style, three luminaries of the DevOps movement deliver a story that anyone who works in IT will recognize. Readers will not only learn how to improve their own IT organizations, they'll never view IT the same way again.

Visible Ops is a methodology aimed at enhancing controls and process improvement in IT organizations, focusing on increasing service levels, security, and auditability while managing costs. It comprises four prescriptive steps that guide organizations from any starting point to a state of continuous improvement. While ITIL offers valuable best practices, it lacks clear implementation guidance, making it challenging for organizations to know where to begin. The Visible Ops booklet provides a practical roadmap for those starting or advancing their IT process improvement journey. Developed in response to the common question of how to initiate IT process improvement, Gene Kim and Kevin Behr studied eight high-performing IT organizations since 2000, identifying key processes that led to their success. The Visible Ops methodology outlines these processes in four steps: 1. Stabilize Patient, Modify First Response – Address risky changes to reduce Mean Time to Recovery (MTTR) and manage problems effectively. 2. Catch and Release, Find Fragile Artifacts – Inventory assets and services to identify those with low change success rates and high downtime costs. 3. Establish Repeatable Build Library – Implement effective release management to create repeatable builds for critical assets, making it more cost-effective to rebuild than repair. 4. Enable Continuous Improvement – Use metrics to foster ongoing enhancement of Release, Control, a