Select Two (Multi-Select) Questions

SU is optional; IP is mandatory

Why wrong: Both are mandatory in PRINCE2.

SU creates the Stage Plan for the first stage; IP creates the Project Plan

Why wrong: SU creates the Stage Plan; IP creates the Project Plan and detailed Stage Plans.

SU includes the appointment of the Project Board; IP includes the appointment of the Project Manager

Why wrong: The Project Manager is appointed in SU; the Project Board may be formed in SU.

Produce Highlight Reports

Why wrong: Highlight Reports are produced by PM in CS.

Escalate issues to the Project Board

Why wrong: Escalation is done by PM in CS; Board receives escalations but does not perform escalation.

Manage product delivery

Why wrong: Managing product delivery is done in MP by Team Manager.

Producing Checkpoint Reports

Why wrong: Checkpoint Reports are from Team Manager.

Managing the day-to-day activities of the project team

Why wrong: That is the PM's role in CS.

Project Plan

Why wrong: The Project Plan is created in Initiating a Project.

End Project Report

Why wrong: The End Project Report is created in Closing a Project.

Risk Register

Why wrong: The Risk Register is created in Initiating a Project.

Enhance

Why wrong: Enhance is for opportunities.

Exploit

Why wrong: Exploit is for opportunities.

Increases administrative efficiency

Why wrong: Not a benefit.

Reduces the number of roles required

Why wrong: It adds a role.

Ensures faster decision-making

Why wrong: Not a direct benefit.

Day-to-day management of the project

Why wrong: Day-to-day management is the responsibility of the Project Manager.

Preparing the Highlight Report

Why wrong: The Project Manager prepares the Highlight Report.

Defining the technical specifications of products

Why wrong: Technical specifications are typically defined by the Senior User or Supplier.

Enhance

Why wrong: Enhance is an opportunity response.

Exploit

Why wrong: Exploit is an opportunity response.

Project Brief

Why wrong: Project Brief is produced in SU.

Project Initiation Documentation

Why wrong: PID is produced in IP.

Checkpoint Report

Why wrong: Checkpoint Reports are produced in MP.

Product descriptions

Why wrong: Product descriptions are part of the Quality theme, not the Business Case.

Quality criteria

Why wrong: Quality criteria are part of product descriptions, not the Business Case.

Acceptance criteria

Why wrong: Acceptance criteria are defined by the Senior User, not part of the Business Case.

Problem

Why wrong: 'Problem' is too vague; the correct term is 'Problem/Concern'.

Threat

Why wrong: Threats are risks, not issues.

Quality review

Why wrong: Quality review is a technique, not an issue type.

Can be shared between two people

Why wrong: The SRO is a single role, though can be supported.

Is a member of the project team, not the Project Board

Why wrong: The SRO is a member of the Project Board.

Responsible for day-to-day management

Why wrong: The Project Manager handles day-to-day management.

Technical Lead

Why wrong: Not a defined PRINCE2 role.

Project Sponsor

Why wrong: PRINCE2 uses Executive/SRO, not Sponsor.

Authorizing work packages

Why wrong: This is the Project Manager's role.

Day-to-day management of the project

Why wrong: This is the Project Manager's role.

Project Product Description

Why wrong: Incorrect. The Project Product Description is an input to the Closing a Project process, created during the Initiating a Project process and used to verify that the project product is acceptable.

Benefits Management Approach

Why wrong: Incorrect. The Benefits Management Approach is created during the Initiating a Project process and updated throughout the project, but it is not an output of Closing a Project.

Lessons Log

Why wrong: Incorrect. The Lessons Log is maintained throughout the project and is an input to Closing a Project, but the process output is the Lessons Report, not the Lessons Log.

Project Plan

Why wrong: Incorrect. The Project Plan is created during the Initiating a Project process and is an input to Closing a Project, not an output.

To manage the day-to-day activities of the project

Why wrong: Incorrect. Managing day-to-day activities is the responsibility of the Project Manager, not the Directing a Project process.

To create the Exception Plan

Why wrong: Incorrect. Creating an Exception Plan is performed by the Project Manager, not the Project Board in Directing a Project.

To accept work packages from the Project Manager

Why wrong: Incorrect. Accepting work packages is part of the Managing Product Delivery process, not Directing a Project.

Benefits Management Approach

Why wrong: Benefits Management Approach is produced in IP.

End Project Report

Why wrong: End Project Report is produced in CP.

Project Initiation Documentation

Why wrong: PID is produced in IP.

Manage by phases

Why wrong: PRINCE2 uses the term 'stages', not 'phases'.

Document everything

Why wrong: Not a PRINCE2 principle; the principle is 'Learn from experience'.

Assign all roles to one person

Why wrong: Not a principle; PRINCE2 emphasizes defined roles and responsibilities.

Project Assurance

Why wrong: Project Assurance is appointed during Initiating a Project, not SU.

Team Manager

Why wrong: The Team Manager is appointed later during the process.

Configuration item records

Why wrong: Configuration item records are part of change control.

Quality register

Why wrong: The quality register is a separate management product.

Product descriptions

Why wrong: Product descriptions are part of quality and planning, not the Business Case.