Chapter 13: Introduction to processes

Question 1

What is the definition of a “process”?

Answer 1

A process is a structured set of activities designed to accomplish a specific objective. It takes one or more defined inputs and turns them into defined outputs.

Question 2

How many PRINCE2 processes are there? Name them.

Answer 2

There are 7 PRINCE2 processes.

1. Starting up a project
2. Initiating a project
3. Managing a stage boundary
4. Controlling a stage
5. Managing product delivery
6. Directing a project
7. Closing a project

Question 3

What process are the project board’s activities covered by?

Answer 3

Directing a project process.

Question 4

There is always a trigger for a project (an idea or a need). What is the trigger called within PRINCE2?

Answer 4

A project mandate.

Question 5

What is a project mandate?

Answer 5

A project mandate is an external product generated by the authority commissioning (corporate/programme/customer) the project that forms the trigger for starting up a project.

i.e., A project mandate is a formal request or approval from someone in charge who wants a project to start. It’s like getting the “go-ahead” signal to begin working on a project.

Question 6

TRUE or FALSE:
PRINCE2 requires that project management processes are as simple as possible and that they reflect the needs of the project.

Answer 6

TRUE

Question 7

Processes can be tailored:
a. “up” or “down”
b. “left” and “right”
c. “horizontal or vertical
d. none of the above

Answer 7

a. “up” and “down”

up = additional detailed documentation and discipline can be introduced for high-risk projects

down = concise bullet-point presentations and more informal processes may be adequate for low-risk projects

Question 8

Are you allowed to tailor PRINCE2 Processes?

Answer 8

Yes

As long as:
1. the PRINCE2 principles are upheld
2. the purpose and objectives of the process are not comprised

Question 9

In what way can you tailor the processes (general considerations)?

Answer 9

1. using similar processes to reflect the organization’s project management method
2. adopting methods required by the corporate/programme/customer
3. combining some activities which fulfil related purposes
4. splitting some activities into smaller parts to clarify
5. changing which role is responsible for activity
6. combining, splitting or amending management products
7. increasing granularity of the process model to include more detailed activities where needed