Revised throughout to match the details and requirements of the 2009 PRINCE2 manual and simplified to make it more useful for those who are new to the method, PRINCE2 Revealed, second edition, is the perfect first reference. A readable end-to-end overview of the complex PRINCE2 method that starts from a more accessible level than other detailed manuals, it will ease you into the topic and put the method into a real world context.
I recently did a webinar for IT Governance about using PRINCE2 for small projects. It seemed to go down well and I gave out several templates and examples of case studies that should be useful.
Revised throughout to match the details and requirements of the 2009 PRINCE2 manual and simplified to make it more useful for those who are new to the method, PRINCE2 Revealed, second edition, is the perfect first reference. A readable end-to-end overview of the complex PRINCE2 method that starts from a more accessible level than other detailed manuals, it will ease you into the topic and put the method into a real world context.
To start a project PRINCE2 suggests that a Project Brief is put together from a Project Mandate. Presumably the ‘too bureaucratic’ lobby is happy that whoever wants a project should provide a Project Mandate – or whatever name they wish to give to the information about what they want the project to do, etc. Notice that I didn’t say ‘write’. Many Project Mandates have been word of mouth. So isn’t it necessary to ensure that all the information that you need is there before you dive in? I’m not saying that every bit of specification should be known before a project starts.
The new 2009 PRINCE2 manual is much more tightly written than its predecessors and has made small modifications to a number of areas. It is believed by its authors to be less prescriptive than earlier versions. But there are some readers who think that is a little too bureaucratic in some documents and leaves a few areas less than fully explained.
