Managing Stage Boundaries

From IT frameworks

Contents 1 Managing Stage Boundaries (SB) 1.1 Purpose & Description 1.2 Objectives 1.3 Inputs 1.4 Outputs 1.5 Hints and Tips 2 Sub-processes

Managing Stage Boundaries (SB)

Purpose & Description

• This process ensures a controlled end of a stage, and planning for the next
• This process is normally triggered once by IP and several times by CS depending on the size of the project
• The Project Manager carries out the process’ activities in preparation for the Project Board’s go/no go decision

Objectives

• To assure the Project Board that the previous stage has been completed as agreed
• To provide information to the Project Board confirming that the project still is viable
• Produce a Next Stage Plan

Inputs

• PID
• Project Plan
• Stage Plan
• Business Case
• All project logs

Outputs

• Next Stage Plan
• Exception Plan
• End Stage Plan
• Updated Project Plan
• Updated project logs
• Updated Business Case

Hints and Tips

• Remember to include both internal and external products in the NSP
• Always update the logs actively. They are of great value during and after the project

Sub-processes

• SB1 Planning a Stage
• SB2 Updating a Project Plan
• SB3 Updating a Project Business Case
• SB4 Updating the Risk Log
• SB5 Reporting Stage End
• SB6 Producing an Exception Plan