Colin Bentley Former Chief Examiner

OGC PRINCE2 Exam Examples By Colin Bentley

Colin Bentley has been a project manager since 1966 and has managed many projects, large and small, in several countries. He has been working with PRINCE2, PRINCE and its predecessor, PROMPT II, since 1975. He was one of the team that brought PROMPT II to the marketplace, wrote the major part of the PRINCE2 manual and is the author of all revisions to the manual until the 2009 version.

He was the Chief Examiner for PRINCE2 from its beginning until 2008 and wrote all Foundation and Practitioner exam papers and marked them until they reached the massive volumes that are sat today. Now retired, he has had over twenty books published, lectured widely on PRINCE2 and acted as project management consultant to such firms as The London Stock Exchange, Microsoft Europe, Tesco Stores, Commercial Union and the BBC. He still writes books on the PRINCE2 method and has updated them all to reflect the 2009 version.

Colin's Blog

PRINCE2 with small projects

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.

PRINCE2 Revealed

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.

Purchase: PRINCE2 Revealed

PRINCE2 Wisdom

IS PRINCE2 TOO BUREAUCRATIC? PART 2

Let’s have a look at other aspects of this ‘bureaucracy’, the registers. PRINCE2 suggests three; a Risk Register, an Issue Register and a Quality Register. Risks are surely so important that we need to collect them together? If nothing else, it gives us a quick-to-read summary of how many serious risks we have, what we need to be communicating to the Project Board for their assessments. And a condensed view of all risks may reveal that two or more risks or risk actions that are proposed might together represent a new risk or create an unacceptable situation. With regard to the Issue Register, I have been in too may projects where there was no standard form (i.e. definition of the set of information required when submitting an issue) and no central collection point not to appreciate the need for the Issue Register. How else will you ensure that everyone can see what everyone else has raised?

Search form

Colin Bentley Former Chief Examiner