PRINCE2-7-Practitioner Sample Questions & Answers

This statement is true. A key update in PRINCE2 7 is the integration of a central 'people' element. It's not a standalone topic but is woven into the fabric of the method, affecting how project managers should lead teams, engage stakeholders, and foster a positive project culture when applying all other parts of PRINCE2.

Tailoring involves adapting the method to the project's environment, size, and complexity. For a small, straightforward project, it is common and appropriate to combine roles on the Project Board, provided there is no conflict of interest. If the budget holder (Executive accountability) is also the primary representative of the users, combining these roles is an efficient tailoring decision. This maintains the three essential interests (business, user, supplier) on the board without unnecessary bureaucracy.

The 'learn from experience' principle is forward-looking. The primary purpose of the Lessons Report at the end of a project is to consolidate all lessons learned (both positive and negative) so that they can be reviewed and acted upon by the wider organization. This helps prevent future projects from repeating the same mistakes and allows them to adopt successful practices, thereby improving corporate capability.

PRINCE2 7 emphasizes the importance of proactively managing team dynamics. Co-creating a team charter is a powerful technique that gives the team ownership of their working agreements. It allows them to collectively decide on communication methods, meeting etiquette, and how to handle disagreements. This builds trust and creates a foundation for effective collaboration, directly addressing the identified conflicts.

A contingent plan (or 'Prepare contingent plans' response) is the most suitable strategy here. The event is uncertain but has a high probability. It would be inefficient to immediately increase the scope and cost to aim for 30% if it's not required. Instead, the project should plan for the possibility. This involves identifying the actions needed to reach the 30% target and setting them aside to be triggered only if the risk materializes.

The 'manage by exception' principle gives the Project Manager authority to manage the stage as long as it remains within the tolerances set by the Project Board. The correct application is to use the agreed change control procedure to assess and implement approved changes, while constantly monitoring the forecast against stage tolerances (time, cost, scope, etc.). As long as the cumulative impact of these changes does not threaten to breach tolerance, the Project Manager can continue to manage the situation without escalating to the Project Board.

The PRINCE2 Project Board must represent the three primary stakeholder interests. The Executive represents the business interest (ensuring value for money), the Senior User represents the interests of those who will use the final product, and the Senior Supplier represents the interests of those designing and building the solution. These three roles are mandatory for a compliant Project Board structure.

The 'Purpose' section is critical as it explains why the product is needed and what it contributes to the overall project objective.

The 'Quality Criteria' are measurable definitions of the product's quality attributes. They are essential for quality checking and formal acceptance.

The 'Managing a Stage Boundary' process requires the Project Manager to provide the Project Board with two key pieces of information: 1) The End Stage Report, which shows how the completed stage performed against its plan (including the budget overrun and time gain). 2) The Stage Plan for the next stage, which details the plan for the upcoming work. This combination of past performance and future plans allows the Board to make an informed decision.

This new requirement is a 'Request for Change' because it alters the project's baseline scope. The correct procedure is: 1. Capture it formally. 2. Examine its impact on the project's performance targets (cost, time, scope, etc.). 3. Propose options for dealing with it. 4. Escalate it to the appropriate level of authority (the Change Authority or Project Board) for a decision. 5. Implement the decision.