Jul 31, Alexis Medina rated it really liked it. The book is short, well summarized, easy readable without all the paraphernalia of most ITIL books. The book have a lot of information about running a well-organized IT department. Most of the advices in the book are those we already know, but -sometimes- we are unable to see from the inside of an IT department. I work as a IT manager of a medium-size company, so this books gav The book is short, well summarized, easy readable without all the paraphernalia of most ITIL books.
All the information of this book can be applied to small to medium size companies. Jan 21, Pete Olds rated it it was amazing.
I have long been a believer that books are to be shared. I spent a lot on this book with a weird format and less than pages, and since I have done that, I have struggled to keep my hands on it.
In an organisation that is trying had to follow the ITIL framework, most of my colleagues are familiar with the principles, and applying them in practice. This book presents a simple way for those people to see real results quickly, and clarified things in a simple way for non ITIL trained people.
It's I have long been a believer that books are to be shared. It's expensive, and the paper back was really bad quality, but I would still recommend the book and yes, I have bought a couple of new versions for the library. A lot shorter than trying to read a shelf-load of ITIL books if you want to get the gist of what that's all about.
My one concern is that practitioners will take it too literally wrt creating Change Authorization Boards and such, which may make things move too slowly in the web world. Continuous deployment appears to be the future, and we simply need the mechanisms involved to be able to automate the steps outlined here so that we gain tracability, reviewability, and undo-ability for changes.
I wish all IT organizations followed a few more of the steps in here--have strong change management, have a library of standard builds, put your top people into release management, have a problem management group distinct from incident management that reviews changes as step one of problem resolution, don't allow developers to have access to change production systems.
This book is short, succinct, and to the point with simple, actionable steps to produce immediate gains. Jul 29, Pavel rated it it was amazing Shelves: professional. This book should be read by anyone who manages a server in a professional environment.
This book lists some steps at achieving better control of the servers and software related to them and reduce firefighting. The book is short. Appendixes often repeated what was said in main portion of the book. I wish they had a more comprehensive list of software that is related to each step. Jul 05, Greg Damiani rated it it was amazing. Ever been "in the weeds"?
Do you work everyday with layers of management, conflicting priorities, death march deadlines, and eating lunch at your desk? Start by reading this book. Then get your manager to read this book. A compelling methodology for implementing IT best practices. I would give it five stars, but it is a somewhat bloated. Sep 21, Eddie rated it it was amazing Shelves: computers , business , instructional , non-fiction. A very good introduction to beginning the process of creating a governance framework for your I.
Good solid step for the most part. Short, sweet, to the point a little dry but worth the read. If you want a good book to get your IT Ops group back in line, this is the book. It's affordable for the groups that don't have a budget for training material and its a good primer to help you lead your group back to sanity! Mar 24, Ivan Dimitrov rated it it was amazing.
Excellent read. Clear ideas and presents steps on how to acheive them. Must read for every IT service, not just Ops. I'll be implementing this in my organization Excellent read. I'll be implementing this in my organization Sep 27, Michael rated it liked it. Jun 05, Artbikes rated it it was ok. Boss made me read this. Jun 12, Mike rated it it was amazing. Excellent technical guide. Jan 07, Jaakko Kourula rated it really liked it.
Nov 16, Nicholas Moryl rated it really liked it. Conciso y evidentemente util. Un poco obsoleto en algunos aspectos y demasiado radical. Apr 18, Matthew Brown added it.
This really is a Handbook. There are so many details that you have to get a copy to keep near by once you start implementing the ideas in the book. Aug 11, Rob Roy rated it it was amazing Shelves: non-fiction. Clear direction on implementing IT Service Management.
Fredrik Normen rated it liked it Jan 16, Mohamed Elsweesy rated it really liked it Jul 31, Cassie B rated it liked it Oct 19, How to initiate a… December 8, How Adobe turned operations… October 2, There must be more to change management than bureaucracy, good intentions and scarcely attended meetings. Organizations where, deep down, everyone knows that people circumvent proper processes because crippling outages, finger-pointing, and phantom changes run rampant.
The sense of agility is all too often a delusion. Organizations where both internal and external auditors are on a crusade to find out whether proper controls exist and to push madly for implementing new ones where they are not in place.
Organizations where IT understands the need for controls, but does not know which controls are needed first. Like breaks on a car, controls actually allow you to go faster. A task without a vision is but a drudgery; but, a vision and a task are the hope of the world. Edwards Deming. Visible Ops Handbook, The. Every time a change is made you risk breaking functionality Create scheduled maintenance windows where all changes are made Why?
Scheduled changes are more visible, and are more likely to be planned and tested before going into production Automate daily scans to detect and report changes Why?
0コメント