PRINCE2 – Foundation Exam – Quiz 20

It is to be noted PRINCE2 allows only one Project Manager (and only one Executive).

The Senior Supplier authorizes specialist resources, and the Senior User authorizes any user resource (such as to help specify requirements and take part in testing).

It is to be noted that the work can be covered by the Project Manager, usually in a small project.

It is to be noted that quality assurance is an organizational function, external to the project.

Specifically in the activity ‘Design and appoint the project management team’ comes under starting up a project.

It is to be noted that a release is a collection of items, each with a registered version number, that works together. So in IT, a release could be a computer system of, say, five programs: version 4.5 of program 1, version 4.2 of program 2, version 6.8 of program 3, version 1.7 of program 4, and version 2.9 of program 5. A future release may only have some of the member programs updated, with the remainder being the same as in the previous release.

If this is not done by corporate or program management, the Executive should appoint a suitable person to the role of Project Manager.

It is to be noted others can contribute and support but the responsibility lies with the Project Manager.

The three types of project insurance are
I: Business
II: User
III: Supplier

It is to be noted Plan Monitoring must be Project Manager-independent. It is fine for one person to be the Project Board on a very small project and to cover all three board roles.

It is to be noted the term ‘strategy’ is a gift for any aspect of ‘how’ something is going to be done, and for PRINCE2 that is risk, quality, configuration management (actually, how all changes are going to be managed) and communication.

It is to be noted a representative of a program may attend board meetings, but that is not a board position, so quality or other obligations are not specified in PRINCE2.

The Overview of the Project Product Description (PPD) is created an early-in Start-Up. The customer quality expectations will continue to be included in the Project Initiation Documentation (PID), but ‘first recorded’ is specified in the question. There’s no such thing in PRINCE2 as the Project Output Register, by the way. There are quality records and although they can go to a file, that file is not a PRINCE2.

Verify products that are fit for purpose completes the purpose statement for the Quality theme? The purpose of the Quality theme is to define and implement the means by which the project will create and:

The executive is not a role in a PRINCE2 Quality Review.

It is noted that more rote learning of terminology, although this term is more readily understood – and so memorable – than some others in the topic of Quality.

The preparation of the strategy is covered by the Initiating a Project process, which in turn is part of the Initiation Stage work carried out.

Quality Assurance is outside of the project while Project Assurance is inside the project and accountable to the Project Board – or members of the board are doing it themselves. Project Assurance is independent of the Project Manager, but the quality assurance is independent of the project as a whole, including its Project Board.

It is to be noted that comments may be submitted to be placed on the agenda for consideration prior to analysis. That means people need to get the product on time

It is to be noted the new system must have 99 percent availability with 1 percent maximum downtime would be a suitable entry in a project’s Acceptance Criteria

The plan may be checked by Project Assurance, but it’s approved by the board. Any plan at the project or stage level must have Project Board approval.

This supports the principle of ‘focus on products’.

It is to be noted that Just the Project Plan is included in the Project Initiation Documentation (PID).

It is to be noted plans for exceptions aren’t standard. An exemption plan is usually at the level of a point, but maybe at the level of a project or include more than one phase.

The Project Manager submits an End Stage Report for the job that has just been completed along with a Next Stage Plan or an Exemption Plan for the remainder of the current stage.

It is to be noted product descriptions for all identified products are written, and as soon as possible after the product needs are identified.

It is to be noted the keyword is ‘flow’.

It is to be noted stage planning is covered by the Managing a Stage Boundary process which is triggered at the end of each stage except for the final stage of the project. When there is no other stage to plan, the Closing a Project process is instead called.

It is to be noted PRINCE2 takes a product-based or product-led approach to planning, but that doesn’t mean that other plans aren’t needed, just that the products are done first. An external product is something coming over the boundary of the project from outside. An external product is needed on the project, or it wouldn’t be included in the diagrams.

It is to be noted that all the PRINCE2 reports have the word ‘report’ in their title, with the sole exception of the Product Status Account. If you haven’t learned as far as change control, don’t worry about the Product Status Account . . . yet. The Highlight Report is the regular progress report sent by the Project Manager to the Project Board members and then to any other people designated in the Communications Management Strategy.

It is to be noted there’s a response that’s ‘rejecting’ and maybe, unfortunately, starting with an ‘R’ as well. This is where acronyms such as AS RAFT and SEER only serve as memory joggers since you still need to remember exactly what the acronym letters stand for. A nasty question but to make the point about being sure of the acronyms is included here.

It is to be noted in PRINCE2 the risk management is not optional. The Regular Log documents risks found during Start-Up, including when there is a strong need for structured monitoring of them. During initiation, the risks are then transferred to the Risk Register, when the Risk Register is available. Everyone, including Team Managers, is interested in recognizing risk. When doing team plans, team managers can also spot risks.

It is to be noted threats for negative risks, opportunities for positive risks.

It is to be noted this question shouldn’t have been a problem unless all the PRINCE2 management products swim in your head and you start losing focus on what they all are about. The team members are not interested in the preparation of Checkpoint Reports or Highlight Reports. There’s no such thing as a Risk Report in PRINCE2. If products are starting to swim around, try to stand back a bit in your revision and

It is to be noted that first two things for risks are that they need to be identified and controlled; the third thing is that it needs to be assessed.

It is to be noted that you need to be familiar enough with things like definitions, so you can quickly and accurately pick the right words. The keyword for risk is ‘uncertainty,’ so if you weren’t sure this is a good indication here.

It is to be noted that resource is not part of the PRINCE2 risk management procedure.

It is to be noted that the Risk Register is created during the Initiation of a Project process, not during Start-Up, and when the Risk Management Plan is being formulated.

It is to be noted that proximity is another measure but that is not mentioned in the question. Probability and impact are common risk management measures in general and not just PRINCE2, hence the P – I Matrix.

It is to be noted that ultimately the Executive is responsible, though others may be doing risk-related work and have input.