PRINCE2, ITIL, Agile … can I have the best of all?
April 14, 2011
Posted by on
There is a lot of discussion about what the best methodology is to adopt for an organisation. As soon as the discussion moves in that direction, it moves away from realities of any Software Development Life Cycle (SDLC). Projects simply do not mushroom out of thin air. Something causes a realisation in the organisation that moves them to mobilize and start a project. The project than needs monitoring and control to bring the desired transformation in the organisation.
In an IT Service Management context, this realisation would come from the Continuous Service Improvement (CSI) process in ITIL. CSI should highlight required areas for improvement. That should in turn form the business case for a project in an PRINCE2 Start Up process. Once the business case has been approved, ITIL Service Design strategies can be used to initiate the project and plan the product catalog. PRINCE2 being a project management framework, does not specify how the specialist products are produced. Therefore, subsequent development stages can now be executed using Agile methodology. Agile and PRINCE2 both recognize the folly of planning too far ahead. During the iteration deployment, the ITIL Service Deployment strategies can be used. Each iteration length can be used as individual management stages.
Credits: ITIL from OGC, PRINCE2 adapted from OGC, Agile: Mountain Goat Software – click to view larger
PRINCE2, ITIL and agile methodologies all come from a desire to implement successful projects. All of these come from many years of learning by many involved in the SDLC. Each have their unique strengths. When the entire life cycle is taken into account, they can all fit nicely in their own areas.
Yes indeed, you can have the best of all 3.