Reddit Reddit reviews The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps

We found 17 Reddit comments about The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps. Here are the top ones, ranked by their Reddit score.

Computers & Technology
The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps
Used Book in Good Condition
Check price on Amazon

17 Reddit comments about The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps:

u/oooeeeoooahhahh · 8 pointsr/ITManagers

Umm.. It's a framework.


This is the book you're looking for.


u/chimney3 · 6 pointsr/sysadmin

Read this book:

It's short and provides excellent guidance through the process of stabilizing a fragile environment. It saved my life at my last job and ensured that my current job never got crazy to begin with.

u/tritoch8 · 5 pointsr/sysadmin

The Visible Ops Handbook, no one has mentioned ITIL yet and this is a great summary of what it is and how to implement it.

u/somahaiken · 3 pointsr/sysadmin

I highly recommend starting with The Phoenix Project. Don't pass by this book just because it says "DevOps" in the title. It quite specifically addresses the ideas of change management, why they are important for IT, and more importantly why they are important for the business.

Then once you're sure you're ready for Change Management, The Visible Ops Handbook is a more prescriptive book that will help you on the beginning stages of implementing Change Management.

u/whinner · 2 pointsr/sysadmin

I used it too. Passed in about a week. As others have said, it's mostly a vocabulary test. I would also recommend reading through

I read this a year or so ago and it really helped in understanding WTF they're talking about.

I would also recommend you force yourself to disregard the word "service" through most of the lectures. For example, the 5 phases are:

  1. Service Strategy
  2. Service Design
  3. Service Transition
  4. Service Operation
  5. Continuous Service Improvement

    When I first read through the official material, it's gets confusing because everything is Service. Remove the word Service from the list and it's much less confusing.
u/paul_h · 2 pointsr/agile by my boss Kevin Behr and his co-authors. Also by the same trio. In the latter the opposing factors of planned and unplanned work. Planned work, us in development would think of as stories, epics, etc in a card/wall/board centric app. Unplanned work: tickets in a incident/problem management app. You have to attend both of course, and work to minimize unplanned work. ThePhoenixProject is TheGoal but 30 years later and skewed towards IT (while still in a manufacturing company, with it's own bricks and mortar outlets), and contrasting planned and unplanned work, as I said. VisibleDevOps talks of ITIL, which ties in the "Managing IT operations" you were asking about.

u/Darkmere · 2 pointsr/talesfromtechsupport

CM is the single most important thing to avoid random outages. Proper CM will create a log of whatever changes happen, and allow you to follow through with analysis of whatever went wrong when it does.

If you ever get into your mind that you dislike CM, look up The Visible Ops Handbook

u/cat5inthecradle · 2 pointsr/ITManagers

Check out The Visible Ops Handbook

It describes a dead simple 'catch and release' program.

Make a spreadsheet, pick a couple of key details that apply to all assets (name, model, serial, location). Start capturing things. Make a google form for it if you want, and send a tech to the server room with the form up on a laptop to capture everything.

Worry about organizing and displaying this information later, just get all of your assets identified first. Any specialty software worth it's salt will have an import function.

u/digitalchaos · 1 pointr/sysadmin

Fuck that. Just read Visible Ops:
That will give you condensed version of everything you need to know about ITIL except one thing: A near universal truth about people who talk about ITIL is that they have horrible problems... horrible problems that they cannot fix on their own and think that ITIL is fucking magic that you can buy for your shit infrastructure.

The people doing it right are basically doing portions of ITIL yet have never heard of ITIL. One of the big goals of ITIL is to provide a common language for various people who "do it right" but it seems rare to find those instances. Don't ge me wrong... what ITIL proposes is good stuff. It's just the people who chase it seem to have no idea how to do it. Plus I wanted to save you the time and just point you at the cliffnotes version (Visible Ops).

u/aelfric · 1 pointr/sysadmin

If you're interested in change control, then I recommend The Visible Ops Handbok. It's an excellent, short, introduction to how to implement effective change control in an IT environment.

u/ramindk · 1 pointr/linuxadmin

Visible Ops might be your best bet and it's short enough your head pants wearing mgmt might actually read it.. IIRC it should cover than well run system can determine versions globally, upgrade and downgrade cleanly ideally in an atomic transaction, and all the other ITIL fun stuff. ITIL itself may be a bit overblown in implementation, but most of the concepts are useful.

u/FreeDudeFreeFood · 1 pointr/slavelabour

Need this book. $5 for whole book PDF form.

Edit: Got it from bookseller10.

u/idboehman · 1 pointr/devops

Agreed with this too. It's a quick and entertaining read that has a lot of good lessons within. I'd also suggest reading The Visible Ops Handbook by the same authors.

u/michaelhoff · 0 pointsr/sysadmin

Sounds like your boss is just being a dick.

However, from an ITIL perspective, Incident Management and Problem Management are designed to catch these "problems" and share the wealth of knowledge that was gained in order to prevent this problem from happening. Your boss is doing this wrong.

You may want to get him this book. It'll show him how to adjust his monitoring/tracking policies to actually have some benefit to the business. By adopting some ITIL processes, he can actually provide some value to the business, rather than being just a dick.

Don't send him that book if you are an 18-year old consultant who sets up BIND DNS servers w/o documentation.