Tuesday, September 11, 2018

PRINCE2 Quality Management Approach


During Initiating a Project, the project manager is asked to clarify and document the Quality Management Approach as part of the Project Initiation Document (PID). The quality management approach describes how the project will manage quality - what we will do to make sure the projects products are “fit for purpose”?

If you are in an organization with complete and detailed standard operating procedures (SOP) covering quality management, and those produces are well implemented and used, your Quality Management Approach description should be quite slim and should focus on areas where the SOP is weak.

Below are some questions you should ask when clarifying and documenting the Quality Management Approach.

Wednesday, September 5, 2018

Issue Rating Scales

When an Issue is captured, the next step is to examine the issue by undertaking an impact analysis. The impact analysis should include rating the issue on severity and priority, but what scales should you use?

In the PRINCE2 Change Management Approach, part of the Project Initiation Document (PID), you are asked to define the scales for severity and priority. The PRINCE2 Change theme doesn't give you any examples or specific recommendations on which rating levels to use. Here is one suggestion that might help:

Saturday, December 30, 2017

Yes, It is a PRINCE2 Issue




The PRINCE2 Issue Register and the Issue Reports are crucial tools to keep your projects under control. This is where all important decisions and changes are reported and tracked.

Some feel there is a negative connotation to the word “Issue”. As a consequence, they underutilize issue reporting and the issue register. The end result is either poor traceability of decisions and changes, or unnecessary use of additional tools like a “decision log”.

If there is a change request to an already approved baseline, something is not delivered as promised, or guidance or a decision is needed on a problem, then it is a PRINCE2 Issue.

Here is some practical guidance:

Friday, December 29, 2017

Risk Assessment Scales

In the PRINCE2 Risk Management Approach, part of the Project Initiation Document (PID), you are asked to define the scales for probability and impact. In the PRINCE2 Risk theme you find an example using five levels of probability and five levels of impact.

This is a easy and straight forward way of scaling probability and impact, and you can make a nice 5x5 probability impact grid for visual purposes. But, PRINCE2 doesn't give you any help to define the levels of impact. Here is one suggestion that might help:

Tuesday, October 3, 2017

PowerPoint PRINCE2 Project Brief Template


In complex environments with high level of ambiguity, rich content in the shape of a document might be needed to describe objectives, scope, products, approach and roles. But for some projects, the context is known and the project environment quite clear. In these cases more structure can compensate for less rich content, and a PowerPoint slide deck might do the job as a project brief.

Tuesday, January 31, 2017

PRINCE2 2017


Mid-2017, AXELOS launched a new edition of the PRINCE2 guidance. The updated guidance comes with new exams, both PRINCE2 Foundation and PRINCE2 Practitioner.

According to AXELOS, the new PRINCE2 2017 Foundation exam is leaner and more focused on the core of PRINCE2, while PRINCE2 2017 Practitioner is focusing on the practical skills. If you trained and certified on PRINCE2 2009 Edition, should you retrain for PRINCE2 2017?

Wednesday, January 4, 2017

PRINCE2 Project Brief – Scope vs PPD

PRINCE2 PPD vs PRINCE2 Scope

A common challenge in PRINCE2 Project Briefs and PRINCE2 Project Initiation Documents (PID) is that the Project Product Description (PPD) is repeating too much of the Scope description. Repeating something previously described brings no added value, annoys the reader and potentially draws the attention away from other important points to get alignment on.

In addition, many struggle to get specific on the “Customer’s quality expectations” resulting in a Project Product Description filled with too many general statements. Sounds familiar? If so, the guidance below could be helpful.

Monday, January 2, 2017

When is it a project?


PRINCE2 is only suitable for use on projects, but how do we know if we have a project or if we have “business as usual” (BAU)?

“A project is a temporary organization that is created for the purpose of delivering one or more business products according to an agreed Business Case”. This is the PRINCE2 definition of a project. It is helpful, but the definition is not always sufficient to help you judge if you have a project or a collection of tasks. Below you find some additional help.

Friday, August 5, 2016

A Brief PRINCE2 Project Brief Template

Are you looking for a short and simple PRINCE2 Project Brief Template? If you bombard stakeholders and team members with long and content rich PRINCE2 documents, both you and the PRINCE2 method could be perceived as overly bureaucratic.

Keeping the documents short, writing in bullet points and using tables are useful tricks to signal efficiency and agility.

PRINCE2 – Hierarchy of Requirements


Product based planning is one of the most powerful techniques in PRINCE2, but where do you draw the line on how detailed a product description should be? Unlike PMBOK® Guide from PMI, PRINCE2 doesn’t explicitly deal with requirement management.

Who documents which level of requirements? What goes in the Project Product Description (PPD in the Project Brief and PID), what should be in the Product Descriptions and what do you do with the rest? Here are some advices:

Friday, November 27, 2015

PRINCE2 Agile - Stage vs Sprint.



Stage vs Sprint - PRINCE2 Agile
PRINCE2 Agile - Stage vs Sprint
Those who have worked with agile methods like Scrum, and then are exposed to PRINCE2, can easily jump to the conclusion that a PRINCE2 stage is a Scrum sprint. Both in PRINCE2 Agile theory and in real life the link between a stage and a sprint is usually slightly different. 

Wednesday, November 25, 2015

The PRINCE2 Agile Organization

Organization is one of the seven PRINCE2 Themes and includes definitions of roles and responsibilities at different levels of the project organization. One of the most challenging dimensions of combining PRINCE2 and Agile is to design the organizational interface between the two. PRINCE2 Agile gives us some clear advice on the governance structure and some interface options to choose from. Let us have a closer look at these recommendation and the options.