Skip to content
0 / 66 sessions

Course contents

Module 9 of 13 · 66 sessions

PRINCE2® Foundation

Free
Course overview

Course progress

0%

0 of 66 sessions complete

Sign in to save your progress across devices.

Module 9Session 49 of 6615 minKnowledge check

The issue management procedure

The five steps for handling formal issues, and the records used along the way.

Sign in to track progress
Guided lesson
~0:24Scene 1 of 7

Scene 1

The issue management procedure

The five steps for handling formal issues, and the records used along the way.

Caption 1 of 3

Name the steps in the issue management procedure

0:00 / 0:24
Read all scene text
  1. Name the steps in the issue management procedure
  2. Describe the purpose of the issue register and issue report
  3. Describe the options for responding to requests for change and off-specifications

Scenes animate with GSAP. Use pause or replay at any time.

In this session

  • Name the steps in the issue management procedure
  • Describe the purpose of the issue register and issue report
  • Describe the options for responding to requests for change and off-specifications

It's time to handle Priya's bigger oven request properly.

Let's say Priya emails Sam: the oven in the plan is fine for now, but a bigger one would let York bake for a new wholesale customer too. It costs £3,000 more.

How should Sam handle it?

Select the arrow to learn more

1 of 4

Capture

Sam logs it in the issue register as a request for change and decides it needs formal handling, because it changes the approved equipment list.

The five steps

The issue management procedure has five steps:

  • Capture: record the issue and decide whether to handle it formally or informally
  • Assess: understand its effect on the project's objectives and the business case
  • Recommend: identify the options and recommend a response
  • Decide: the right person decides, whether the project manager, the change authority or the board
  • Implement: carry out the decision and update the affected plans and products

Records

Issues use these records:

  • Daily log: informal issues the project manager handles directly
  • Issue register: every formal issue, with its type, date, status and priority
  • Issue report: a fuller description of a formal issue, its effects and the recommendation, when a decision is needed

Responding to a request for change

For a request for change, the decision-maker can:

  • Approve it, funding it from the change budget, by cutting scope elsewhere or by asking for more money
  • Reject it
  • Ask for an exception plan, if the change would take the project outside tolerance
  • Request more information before deciding

Responding to an off-specification

For an off-specification, the options are:

  • Accept it as it is, without corrective action. This is called a concession
  • Reject it and have it fixed, funded from the change budget, through an exception plan or under the supplier's contract

Key points to remember

  • The issue procedure is capture, assess, recommend, decide and implement.
  • Formal issues go in the issue register; issue reports support decisions.
  • Requests for change can be approved, rejected, escalated by exception or deferred for more information.
  • Accepting an off-specification without corrective action is a concession.
Knowledge checkQuestion 1 of 4

Knowledge check

Choose one answer

Practices

Which step of the issue procedure comes after assess?

Which step of the issue procedure comes after assess?
Choose one answer to continue.

Sign in to save your result. Knowledge checks can be retried any time.

PRINCE2® is a registered trademark of the PeopleCert group. MockAcademy is independent and not affiliated with, endorsed by or licensed by PeopleCert.