30 Aug 2005
Create your methodology based on a standard framework (Part2)
by Lucas Rodriguez Cervera of Nevant
This article, the second of a series of three, gives some tips on adapting anddocumenting a methodology based on a standard framework such as ITIL or PMBoK.
In the previous article I explained why it is a good idea to create a methodology based on a standard frameworkand highlighted the criteria to choose the most convenient one. In this article I will give some tips for theadaptation and documentation of the methodology.
Understand the framework
Once a framework has been chosen it is time to start building the methodology. The first step is to acquire ageneral understanding of the framework, a holistic view of its components. You must have a clear idea of itsscope and boundaries. It might be useful (if you already have some formal processes in place) to carry out amapping of your processes to the standard and perform a gap analysis. This is not necessary if you approach theproject as a reengineering project, building the new processes from the ground up.
Build a roadmap
Once you have a clear vision of the standard framework's scope and your current situation, you have to definewhere you want to get (the scope of your methodology). This means that you must have a clear vision of your organization once the new methodology is in operation. You might find that some processes do not apply to your organization or are too sophisticated for your needs.Be realistic. Take into consideration the resources you have available for the project and the timeframe. Be surethat this strategic vision is known by all people involved in the project and understood and shared by the initiativesponsor.Now you know where you want to get and the objectives of the project have been defined, it is time to plan howyou are going to get there. You can face the project in two ways:
Once-off delivery. The methodology is only only deployed once the full scope has been achieved.
Incremental delivery. The methodology is deployed in several iterations, each of which releases a set of processes.Although the once-off approach can make sense when the scope of the change is limited, I believe an iterativeapproach increases the probability of success of the project. Try to get some quick-wins by choosing for the firstiterations those processes that add visible value or solve a known problems. You will learn with each release andapply that knowledge in subsequent iterations.
Nevant – The link between processes and resultsPag 1