A couple of weeks ao, I attended a presentation on PRINCE2 at my local APM chapter. Rob Smith of PMProfessional Learning ran through what the current PRINCE2 structure is. [For those who don't know, PRINCE2 stands for 'PRojects IN a Controlled Environment' and focuses on the processes to control projects.] So what are the gems of ideas from PRINCE2 that we might want to borrow?

1. It's very logical. If you ever want a comprehensive and thought through process for change control or a list of all of the possible risk categories for your project, then the PRINCE2 manual is invaluable.
2. The idea of breaking a project into manageable chunks, which are then planned, managed and executed. These are called stages in PRINCE2.
3. Management by exception. Give people working for you tolerances and leave them alone (at least, don't micro-manage them!) as long as the results are within tolerance as they are delivered.
4. The business case must drive the project, so the project should stop if the business case is no longer valid.

All this sounds great, but what are the drawbacks?
1. The method can be seen as prescriptive and is very rarely applied fully - PINO is much more common (PRINCE In Name Only)
2. Focussing on process is no longer seen as the way to make projects work, and, in my experience, never has been.
3. The PRINCE2 manual excludes all aspects of people in projects!

At the end of the talk, Rob outlines some of the ideas for the revamp of PRINCE2 in 2009. This is a major change! Next year, the PRINCE2 manual will change from being prescriptive to providing a framework with principles, key themes and a reduced number of processes. It'll cross-reference other ideas and bodies of knowledge.

Wow! I look forward to finding out more... If you know any more and/or you can add to the lists above, please comment!