The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps
著者: Kevin Behr; Gene Kim; George Spafford
|
|
| Paperback: | 112 ページ |
| 出版社: | Information Technology Process Institute |
| 出版日: | 2005年6月15日 |
| ISBN: | 0975568612 |
| ISBN-13: | 9780975568613 |
| 参考価格: | $21.95 |
| 価格: | $21.95 |
| 価格 | - | ¥1,967 | - |
|---|---|---|---|
| 送料 | ¥805 / ¥358 | ||
| 合計 | ¥2,771 / ¥2,324 | ||
| 発送 | Usually ships in 24 hours | ||
| 購入 |
|
||
|
|||
関連商品
- Measuring ITIL: Measuring, Reporting and Modeling - the IT Service Management Metrics That Matter Most to IT Senior Executives
- Visible Ops Security: Achieving Common Security and IT Operations Objectives in 4 Practical Steps
- ITIL V3 Foundation Complete Certification Kit - 2009 Edition: Study Guide Book and Online Course
- Foundations of IT Service Management: The Unofficial ITIL v3 Foundations Course in a Book
- Servicing ITIL: A Handbook of IT Services for ITIL Managers and Practitioners
内容説明
The Core of Visible Ops Visible Ops is a methodology designed to jumpstart implementation of controls and process improvement in IT organizations needing to increase service levels, security, and auditability while managing costs. Visible Ops is comprised of four prescriptive and self-fueling steps that take an organization from any starting point to a continually improving process. Making ITIL Actionable Although the Information Technology Infrastructure Library (ITIL) provides a wealth of best practices, it lacks prescriptive guidance: What do you implement first, and how do you do it? Moreover, the ITIL books remain relatively expensive to distribute. Other information, publicly available from a variety of sources, is too general and vague to effectively aid organizations that need to start or enhance process improvement efforts. The Visible Ops booklet provides a prescriptive roadmap for organizations beginning or continuing their IT process improvement journey. Why Do You Need Visible Ops? The Visible Ops methodology was developed because there was not a satisfactory answer to the question: “I believe in the need for IT process improvement, but where do I start?” Since 2000, Gene Kim and Kevin Behr have met with hundreds of IT organizations and identified eight high-performing IT organizations with the highest service levels, best security, and best efficiencies. For years, they studied these high-performing organizations to figure out the secrets to their success. Visible Ops codifies how these organizations achieved their transformation from good to great, showing how interested organizations can replicate the key processes of these high-performing organizations in just four steps: 1. Stabilize Patient, Modify First Response – Almost 80% of outages are self-inflicted. The first step is to control risky changes and reduce MTTR by addressing how changes are managed and how problems are resolved. 2. Catch and Release, Find Fragile Artifacts – Often, infrastructure exists that cannot be repeatedly replicated. In this step, we inventory assets, configurations and services, to identify those with the lowest change success rates, highest MTTR and highest business downtime costs. 3. Establish Repeatable Build Library – The highest return on investment is implementing effective release management processes. This step creates repeatable builds for the most critical assets and services, to make it “cheaper to rebuild than to repair.” 4. Enable Continuous Improvement – The previous steps have progressively built a closed-loop between the Release, Control and Resolution processes. This step implements metrics to allow continuous improvement of all of these process areas, to best ensure that business objectives are met.
カスタマーレビュー
日本
米国
- レビュー数: 42件
- 平均評価:

Concise and Easy to Understand
Great resource for organizations looking to adopt ITIL processes in an effort to mature their IT organization.
If You Only Have Time For One Book On Computer Operations, This Is It
After 15 years as a professional system administrator and manager, I thought I had seen all the good books on the subject, but I have never before seen a short summary of what usually goes wrong and how to fix your processes so that things stop breaking. This book is invaluable to getting everyone rowing in the same direction with understanding how and why complex computer systems break.
One of the things that is always hard to explain to both developers and management is the importance of managing change. It is almost always unplanned change that causes your major problems and Spafford explains this in a funny and accessible way. It is always a challange to "push back" at the business and make them understand the real cost of not having adequate testing and controls in place. This book really helped me both clarify your own thinking on the topic and make a good case to the developers and business owners. This book would especially be useful for someone who worked at a start-up or other unstructured environment and who didn't know where to start first.
I bought 15 copies and gave one to every programming manager at my job as well as all my direct reports. I with I had gotten more!
Right in the Sweet Spot
This product mentions and addresses so many of the struggles that we are having at this point. I asked my boss to read it - his reaction after just the first few chapters - "This is like reading our mail" For anyone that is overwhelmed on where to start and some practical information - this is for you.
ITIL Ops
Great book. Very good high level and mid level insight into ITIL. Good examples and an easy read.
Outstanding - If you are responsible for a data center or IT shop this is a must read
I'm not huge on a one size fits all. In IT there is an exception to every rule, but The Visible Ops is something that could help any IT group. The eye opening statistic is that 80% of outages are operator induced. That's a huge number and obviously leaves a lot of room for improvement. This book goes over the basic steps that are required to stabilize and improve your data center. It's short (95) pages and offers an ITIL compliant framework for making your changes (or more specifically, stopping them from being made with out forethought). I started as a system administrator and I hate the idea of following procedures instead of "just fixing things".
Stability is what your customers look for in their computing environment as well as flexibility. Are you providing both?





