The basics of ITIL are very simple. No—really! That’s where this post on Joe the IT Guy begins—and with good reason. As the author explains, the complications that come in ITSM are often not the fault of ITIL—rather they are the fault of projects that are too large and filled with bureaucratic processes. This is the first lesson that the author shares: the approach shouldn’t be huge:
The biggest mistake here is probably in trying to do everything perfectly in one big project. We have all seen the value that can be created by using Agile methodology to deliver business projects, but too few IT departments think about how a similar approach could be used to deliver ITSM projects. The advantage of this approach is that it allows us to deliver something very fast, and then to incrementally add value. This also allows the detailed requirements to evolve over time, without having to fully understand all the ways we might work in the future before we start.
Perfection isn’t Perfect
The lesson here is to not try to have a perfect project from the start, but rather to choose something that you can create and find value in, and work on that specifically. The article calls this “minimum viable capability”. Doing the minimum amount to start with—more or less to learn how to apply ITIL to a project—is much more preferable than trying to implement the entirety of ITIL to the first project. From that first project, you’ll have a platform to build on. Incremental improvements are the most beneficial and longest lasting.
Read the full article here: http://www.joetheitguy.com/2014/04/27/itsm-doesnt-have-to-be-complicated/