PRINCE2 roles - Project steering commitee / board
Universal Practical Simple Benefit focused Principles Implement Templates Ready apps for Jira
Project steering commitee is established by Project owner/executive based on the need to 1) establish professional project steering, 2) strong project decision authority & 3) involve business, user & supplier key interests. Project owner/executive keeps single person decision authority within Project steering commitee but business, user, supplier stakeholder involvment in project steering decisions have significant impact on project success.
Essential responsabilities in the project:
No. | Responsabilities |
---|---|
1 | Take project start decision by approving draft Business case |
2 | Take next stage decision by approving next stage plan |
3 | Take project delivery decision by approving project plan, Business case & Benefit plan |
4 | Ensure that project deliver maximum benefit based on Business case & Benefit plan |
5 | Get approval for project benefit KPI from Top management (if needed) |
6 | Take decision to establish Change authority (if needed) |
7 | Approve project procurements |
8 | Take decisions on project changes |
9 | Take decisions on critical & important project risks. Delegate mitigation actions with limited authority |
10 | Escalate critical project issue & deviations to Top management |
13 | Communicate project execution status to Top management on strategic level |
14 | Provide consultations & take ad-hoc decisions requested & needed for Project manager |
15 | Take project closure decision with updated Benefit plan |
16 | Communicate project deliveries & results including benefit to Top management & other stakehoders on strategic level |