SB - Managing a Stage Boundary

The purpose of the Managing a Stage Boundary process is to enable the Project Board to be provided with sufficient information by the Project Manager so that it can review the success of the current stage, approve the next Stage Plan, review the updated Project Plan, and confirm continued business justification and acceptability of the risks

+ Show the guide to completing the Maturity Model criteria questions
Compliance
Yes
- There is evidence that the project complies to the criteria

No
- There is no evidence that the project complies to the criteria

N/A
- This criteria does not apply via the use of tailoring or other justifiable reasons
Quality
Red
- The is no evidence or the evidence does not comply with the PRINCE2 methodology

Amber
- The evidence is reasonable, but could benefit from significant improvement to comply fully with PRINCE2

Green
- The evidence complies fully with PRINCE2

N/A
- This criteria does not apply via the use of tailoring or other justifiable reasons


  1. SU
  2. IP
  3. PL
  4. SB
  5. CS
  6. MP
  7. DP
  8. CP
  9. Report
Managing a Stage Boundary (SB)
Project Name:
Please enter a project name, this will be used to load and save your data, so please remember it!
Criteria Question Compliance Quality
Planning a Stage
Is there a next stage plan for each defined management stage?
Are stage plans completed and include all planning criteria (listed in the planning section)?
Is next stage planning carried out toward the end of the preceding stage?
Are stage plans consistent with the project plan?
Are stage tolerances documented?
Are planning assumptions documented?
Is time and effort allowed for project management activates?
Is time allowed for the analysis of project issues?
Has a reasonable rate of resource effort been chosen within the plan?
Have the stage plans been subject to a documented QA review?
Have the stage plans been approved by the project board and authorisation
given to proceed?
Is the baseline stage plan subject to configuration control and management?
Is the current stage plan up to date?
Are stage check point reviews planned to confirm the stage is on track?
Does the stage plan include management products?
Does the stage plan include project specialist products?
Does the stage plan include QA review schedule?
Does the stage plan include key communication activity?
Does the stage plan include checkpoints to confirm the project is on track?
Updating a Project Plan
Has the project plan been updated to account for exception plans?
Has the project plan been updated to account for detailed stage planning?
Updating a Project Business Case
Has the business case been updated (where necessary) at project stage ends?
Updating the Risk Log
Have stage plan risks been identified in the risk log?
Have risks been reviewed and identified at each project end stage?
Reporting Stage End
Is there an end stage report?
Has the end stage assessment been conducted to account and recorded in the end stage report?
Has the lessons learnt log been updated?
Has the communications plan been updated?
Have configuration item records been updated?
Have the stage end report been subject to a documented QA Review.
Has the end stage report been approved by the project board?
Was the next stage plan approved by the project board with authority to proceed?
Producing An Exception Plan
Have exception plans been produced following exception reports?
Have exception plans been presented and approved by the Project Board?
Maturity Model Rating For This Phase
Level 1 - Initial
• Methodology is not being adopted
• Project success very unpredictable
Level 2 - Managed
• Partial adoption of methodology
• Project success unpredictable
Level 3 - Defined
• Variable adoption of methodology
• Some project predictability
Level 4 - Quality
• Good adoption of methodology
• Projects generally predictable
Level 5 - Optimised
• Full adoption of methodology
• Project very predictable
Phase Analysis