The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps Paperback – June 15, 2005
|New from||Used from|
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Frequently bought together
What other items do customers buy after viewing this item?
The easy mapping between the Visible Ops phases and any maturity model validates the compelling logic of the book. --Jan Vromant, ITSM Consultant, May 2004
Visible Ops creates a logical starting point and details the key ‘issues and indicators’. --Henry E. Wojcik, Network Data Systems, May 2004
About the Author
There was a problem filtering reviews right now. Please try again later.
The authors are one of the first to offer in print some solutions for infrastructure support that validate what IT infrastructure managers have been doing for years. The ideas of rebuild v. repair, "source control" of infrastructure builds, repeatable infrastructure build processes are right on. Yet instead of case studies and further exploration, we get multiple pages of testimonials, a forward, an introduction, a multiple-page TOC, a mere 40 pages of content which include repetition, constant summarization, and more testimonials, and 30 pages of appendices of largely copyrighted and incomplete material. As a final insult, there are ads on the front and back covers. At least one of the authors sells tools to remedy some of the problems mentioned in "Visible Ops" and it seems he is hedging his bets by charging for materials that should be marketing and product literature.
Why not give more detailed examples and case studies, expound on the CMDB, give some ideas on organizing builds or address other ITIL areas? This is *great* stuff here, but I feel like it has been cheapened. Regardless, I recommend "Visible Ops" because it addresses common and significant problems and solutions that are rarely addressed elsewhere.
You almost need a magnifying glass to read it.
On top of that, it is only 99~ pages so it is pretty thin. Not sure how well it is going to cover its content.
Stability is what your customers look for in their computing environment as well as flexibility. Are you providing both?
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!
Top international reviews
1) Stabilize the patient
2) Catch and release, and find fragile artifacts
3) Establish repeatable build library
4) Enable continuous improvement.
A highly recommended book.
The frustrating thing is that this is clearly a good book. That much is obvious in spite of the Kindle edition's myriad problems.
Save your money and buy the paper version instead.
Is a nice 'thechnical' handbook, recommended as a follow up of 'the phoenix project'