Change authority and change budget
How the board delegates change decisions, sets a change budget and prioritises issues by severity.
Scene 1
Change authority and change budget
How the board delegates change decisions, sets a change budget and prioritises issues by severity.
Caption 1 of 3
Explain how change authority is delegated
Read all scene text
- Explain how change authority is delegated
- Explain the purpose of the change budget
- Use priority and severity to decide who handles an issue
Scenes animate with GSAP. Use pause or replay at any time.
In this session
- Explain how change authority is delegated
- Explain the purpose of the change budget
- Use priority and severity to decide who handles an issue
It's time to decide who can approve which changes on York.
Let's say Sam brings five small change requests to the board meeting: a different tile colour, an extra plug socket, a second coat hook and two more. Each costs under £200. The board spends 40 minutes on them, and has no time left for the damp.
How could the board spend its time better?
Select the arrow to learn more
1 of 4
Set limits
The board agrees that Sam can approve any change up to £500 and with no effect on the opening date.
Delegating change authority
The project board is the default change authority. It can delegate some of that authority, for example to the project manager or to a small group, with clear limits on what they can approve.
The level of delegation is agreed in initiation and recorded in the issue management approach. It can be reviewed at each stage boundary.
The change budget
The change budget is money set aside to pay for approved changes. It's separate from the risk budget, which pays for risk responses.
Without one, every small change would need fresh approval for funds, or would quietly eat into the stage budget and push it towards its tolerance.
Priority and severity
Issues are given a priority, for example using MoSCoW, and a severity, which describes how serious they are. Severity decides who handles them:
- Low severity: the project manager, from the daily log or issue register
- Medium severity: the change authority, within its limits
- High severity: the project board
- Beyond project tolerance: the business layer
The issue management approach
All of this is written down in the issue management approach, created during initiation. It covers the procedure, the records, the change authority, the change budget and the scales for priority and severity.
For the app, the approach gives Ana's team more freedom: they can reorder features in the backlog between cycles without a formal change, as long as the cycle's time and cost stay fixed.
Key points to remember
- The project board can delegate change decisions to a change authority within limits.
- The change budget pays for approved changes and is separate from the risk budget.
- Priority and severity decide how urgently an issue is handled and by whom.
- The issue management approach is created in initiation.
Knowledge check
Choose one answer
Practices
Who is the default change authority on a project?
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.