Question 1

It is the responsibility of which role to review risk management practices and ensure that they are performed in line with the project's Risk Management Strategy?
A)Project Assurance
B)Project Manager
C)Project Support
D)Executive

Accepted Answer

Project Assurance. This is a key aspect of the Project Assurance responsibilities.
Key takeaway: Project Assurance is there to ensure that the Project Manager is following the various strategies and plans correctly, and subsequently inform the Project Board whether there are any issues or not.

Question 2

A Risk Cause is which of the following?
A)A threat
B)Description of the source of the risk
C)An objective
D)A risk budget

Accepted Answer

A risk cause is a description of the source of the risk.
Key takeaway: When identifying risks, it is important to know the cause (the source of the risk), the risk event (the area of uncertainty in terms of the threat or opportunity), and the risk effect (the impact that the risk would have on the project were it to come about).

Question 3

Which role confirms acceptance of the Project Product?
A)Project Assurance
B)Corporate or Programme Management
C)Project Manager
D)Executive

Accepted Answer

Executive. The Executive has ultimate authority within the project.
Key takeaway: Since the Executive is the owner of the Business Case and is responsible for ensuring the case remains valid throughout the life of the project, it is also their responsibility to provide final acceptance of the Project Product.

Question 4

Follow on action recommendations are made in which process?
A)Starting up a Project
B)Directing a Project
C)Closing a Project
D)Managing a Stage Boundary

Accepted Answer

The Closing a Project stage is when follow-on recommendations are made
Key takeaway: The follow on actions document unfinished business at the end of the project. This is a key step to ensure that future related projects are aware of this unfinished businesses and can deal with the consequences.

Question 5

Which of the following is NOT included in a plan?
A)Dependencies
B)Budgets
C)Schedule
D)Lessons learned

Accepted Answer

Lessons learned. Lessons learned during the execution of a plan could not be documented until the plan was at least under way.
Key takeaway: One of the most under utilized tools is the post-completion Lessons Learned review and meeting. When a project is complete, and especially has gone well, there is a tendency to disregard the need for a Lessons Learned or Postmortem Meeting; but in actuality, the project that has gone well can probably yield the most beneficial information. If it isn't considered a form of performance reporting in your organization, it should be.

Question 6

Which document contains the planned and actual dates for product approval and hand-over?
A)Project Plan
B)Stage Plan
C)Product Checklist
D)Project Brief

Accepted Answer

Product Checklist.
Key takeaway: A Product Checklist is an important tool for a Project Manager. It provides details of the schedule for every product. This will include planned and actual dates for production, quality checks, approval, and handover. Depending on the type of product, it will likely include several more categories. The precise format is flexible. What is important is that it shows at a glance the state products should be in at any given date.

Question 7

A successful project is which of the following?
A)Output-oriented, not activity-oriented.
B)Completed within the original timeframe.
C)One which involves no change.
D)Delivered under budget.

Accepted Answer

Output oriented, not activity-oriented.
Key takeaway: One of the principles of PRINCE2 is the focus on products. This means that any project should be driven by the products themselves, rather than the processes or activities required to produce them. Likewise, the business case should focus on whether the products remain valid throughout the life of the project.

Question 8

Which role confirms stage and project progress against agreed tolerances?
A)Project Board
B)Project Assurance
C)Project Support
D)Project Manager

Accepted Answer

Project Assurance.
Key takeaway: It is the role of Project Assurance to provide independent assurance to the Project Board as to the status of the project. It is for this reason that the Project Assurance and Project Manager roles must not be held by the same person (or people).

Question 9

Which of the following is NOT a PRINCE2 process?
A)Directing a Project
B)Assessing a Project
C)Controlling a Stage
D)Closing a Project

Accepted Answer

Assessing a Project. There is no such process within PRINCE2.
Key takeaway: Assessment is ongoing throughout all aspects of a PRINCE2 project. It is done at all levels, often with reports (e.g. Highlight Reports, Checkpoint Reports) or as a basic function of a role (e.g. Project Assurance).

Question 10

Which PRINCE2 theme addresses the ongoing viability of the different project plans?
A)Quality
B)Plans
C)Change
D)Progress

Accepted Answer

Progress addresses the ongoing viability of the different project plans.
Key takeaway: The Progress theme within PRINCE2 establishes controls that monitor and compare achievements against planned activities. It provides forecasts on project objectives and the continuing viability of the project (in line with the principle of Continued Business Justification), and allows any deviations outside tolerances to be managed and controlled.

Question 11

Which of the following risk responses involves allowing a third party to take on part of the risk?
A)Reduce
B)Avoid
C)Share
D)Transfer

Accepted Answer

Transfer of risk involves allowing a third party to take on part of the risk.
Key takeaway: Transferral of a risk means that a third party takes responsibility for some or all of the financial impact. This could be by means of an insurance policy or clauses in the contract. It is an alternative form of the Reduce option which only affects the financial impact of the threat.
Insurance is inherently about transferring risk. By aggregating individual risks into a pool, insurance companies can protect individual people and firms against risk. This is at a cost, of course.

Question 12

Which role is responsible for producing a Product Status Account?
A)Project Support
B)Project Manager
C)Project Assurance
D)Team Manager

Accepted Answer

Project Support.
Key takeaway: Project Support is primarily an administrative role. It provides information about the project status and advice with tools, along with administrative services such as filing, configuration management, and data collection. It is to Project Support that the Project Manager would turn to for a Product Status Account.

Question 13

The PRINCE2 Quality theme ensures that the projects products:
1)Meet business expectations
2)Are delivered on time
3)Are defined correctly
4)Enable the desired benefits to be achieved subsequently
A)1, 3
B)1, 4
C)3, 4
D)1, 2, 4

Accepted Answer

Meet business expectations and enable the desired benefits to be achieved subsequently.
Key takeaway: The focus on products principle is central to the PRINCE2 approach to quality. By using this principle, there can be a common understanding of the output of a project and how this output will be assessed (i.e. the quality).

Question 14

Which role is responsible for defining and verifying user requirements and expectations?
A)Executive
B)Senior User
C)Project Assurance
D)Team Manager

Accepted Answer

Senior User.
Key takeaway: The three Project Board roles have different responsibilities. While the Executive retains control and is responsible for the business requirements, the Senior User and Senior Supplier are responsible for the committal of user and supplier resources respectively, and are the primary point of contact for any user/supplier issues. This includes defining and verifying requirements.

Question 15

Which of the following is true about stakeholders?
1)They may support or oppose the project
2)They may gain or lose as a result of the project delivery
3)They may actively support or block the project
4)They have a financial interest in the project
A)1, 2, 3
B)1, 3, 4
C)2, 3, 4
D)1, 2, 3, 4

Accepted Answer

A stakeholder need not have a financial interest in the project (although it is certainly possible).
Key takeaway: A stakeholder is not just somebody with an interest in the positive outcomes of the project. It is equally important to identify those stakeholders who are concerned about negative effects, who may oppose the project in some way, or who may be concerned about their own position in the company following the implementation of the project products.

Question 16

Which of the following should always be taken into account when defining the number and length of stages?
1)The project budget
2)Where the key decision points need to be
3)The amount of risk
4)The confidence levels of the Project Manager and Project Board
A)1, 2, 3, 4
B)1, 2, 3
C)2, 3, 4
D)1, 2, 4

Accepted Answer

Although the project budget may play a small role in the decision, it is not one of the key factors.
Key takeaway: When deciding on the number of management stages, it is important to consider the nature and duration of the project. A small project, in which all the work can be easily planned in one stage, would suffer unnecessary cost and time delays with the introduction of extra management stages. Likewise, a large project would become unwieldy and impractical to run in a single stage. The key is to balance all the important factors.

Question 17

The principle of Learning from Experience dictates that everybody involved with the project should examine any lessons learned:
1)When starting a project
2)As the project is in progress
3)When closing a project
4)After the project has closed
A)1, 3
B)1, 2, 3
C)1, 3, 4
D)4

Accepted Answer

Learning from Experience is an ongoing principle.
Key takeaway: When the project is started and the Lessons Log created, the principle of Learning from Experience is applied by documenting lessons from previous similar projects. When the project is closed down, lessons learned within the project are documented for reference in future projects. As the project progresses, it is important to learn from experience on a continual basis, both for reference for future projects and for the continued development of the current project.

Question 18

Which is longer, the product life span or the project life cycle?
A)The product life span.
B)The project life cycle.
C)They are the same.
D)It varies according the projects place in the corporate strategy.

Accepted Answer

The product life span.
Key takeaway: If it takes longer to produce a product than the same product will be in use, then the business case needs to be re-evaluated. The product life span should extend well beyond the life of the project, regardless of where it sits within a programme or the overall corporate strategy.

Question 19

If there is more than one version of a document in circulation, what action should the Project Manager take?
A)Create a new version of the document and issue it to everybody.
B)Halt work until the correct version can be identified.
C)Recall all versions of the document.
D)Request a Product Status Account.

Accepted Answer

Request a Product Status Account. This contains a full status of all project products.
Key takeaway: The Product Status Account is produced by Project Support and contains information about the current state and version of all products. If there is any question about what version should be in use, the first action by the Project Manager should be to request the Product Status Account. This is also a valuable tool when producing End of Stage Reports.

Question 20

When a project is closed, all project information is secured and archived. Why?
A)To allow for future audits.
B)Because project information should never be discarded.
C)In case Corporate or Programme Management wants to review the information.
D)In case the project needs to be re-opened.

Accepted Answer

To allow for future audits.
Key takeaway: Since auditing is not simply a feature of a project (the Quality process deals with the PRINCE2 audit trail for this), a company may be audited on projects long since completed. This process will be documented at a higher level and will depend on which standards the company adheres to. From a project level, it is simply important that the project can be reviewed and audited at some future date.

Quiz 1: Projects in Controlled Environments Foundation

It is the responsibility of which role to review risk management practices and ensure that they are performed in line with the project's Risk Management Strategy?

A Risk Cause is which of the following?

Which role confirms acceptance of the Project Product?

Follow on action recommendations are made in which process?

Which of the following is NOT included in a plan?

Which document contains the planned and actual dates for product approval and hand-over?

A successful project is which of the following?

Which role confirms stage and project progress against agreed tolerances?

Which of the following is NOT a PRINCE2 process?

Which PRINCE2 theme addresses the ongoing viability of the different project plans?

Which of the following risk responses involves allowing a third party to take on part of the risk?

Which role is responsible for producing a Product Status Account?

The PRINCE2 Quality theme ensures that the projects products: 1) Meet business expectations 2) Are delivered on time 3) Are defined correctly 4) Enable the desired benefits to be achieved subsequently

Which role is responsible for defining and verifying user requirements and expectations?

Which of the following is true about stakeholders? 1) They may support or oppose the project 2) They may gain or lose as a result of the project delivery 3) They may actively support or block the project 4) They have a financial interest in the project

Which of the following should always be taken into account when defining the number and length of stages? 1) The project budget 2) Where the key decision points need to be 3) The amount of risk 4) The confidence levels of the Project Manager and Project Board

The principle of Learning from Experience dictates that everybody involved with the project should examine any lessons learned: 1) When starting a project 2) As the project is in progress 3) When closing a project 4) After the project has closed

Which is longer, the product life span or the project life cycle?

If there is more than one version of a document in circulation, what action should the Project Manager take?

When a project is closed, all project information is secured and archived. Why?