Difference between revisions of "Controlling a Stage"

From PRINCE2 wiki
Jump to: navigation, search
(Reference)
(Inputs)
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
''This article is also available in [http://it.prince2.wiki/Controllo_di_una_Fase Italian], [http://es.prince2.wiki/Control_de_una_Fase Spanish], [http://pt.prince2.wiki/Controlling_a_Stage Portuguese].''
+
''This article is also available in [http://it.prince2.wiki/Controllo_di_una_Fase Italian], [http://es.prince2.wiki/Control_de_una_Fase Spanish], [http://pt.prince2.wiki/Controlling_a_Stage Portuguese], [http://fr.prince2.wiki/Contr%C3%B4ler_une_S%C3%A9quence French], [http://ru.prince2.wiki/%D0%9A%D0%BE%D0%BD%D1%82%D1%80%D0%BE%D0%BB%D1%8C_%D1%85%D0%BE%D0%B4%D0%B0_%D0%B2%D1%8B%D0%BF%D0%BE%D0%BB%D0%BD%D0%B5%D0%BD%D0%B8%D1%8F_%D1%81%D1%82%D0%B0%D0%B4%D0%B8%D0%B8_%E2%80%93_%D0%BF%D0%B5%D1%80%D0%B2%D0%B0%D1%8F_%D1%81%D1%82%D0%B0%D0%B4%D0%B8%D1%8F_%D1%80%D0%B5%D0%B0%D0%BB%D0%B8%D0%B7%D0%B0%D1%86%D0%B8%D0%B8 Russian].''
  
  
 
== Purpose ==  
 
== Purpose ==  
 +
 
The purpose of the Controlling a Stage process (CS) is for the [[Project Manager]] to assign the work to be done, monitor this work, deal with issues, report progress to the [[Project Board]] and take corrective action to ensure that the stage remains within tolerance.   
 
The purpose of the Controlling a Stage process (CS) is for the [[Project Manager]] to assign the work to be done, monitor this work, deal with issues, report progress to the [[Project Board]] and take corrective action to ensure that the stage remains within tolerance.   
  
Line 9: Line 10:
  
 
== Objective ==
 
== Objective ==
 +
 
The objective of the Controlling a Stage process is to ensure that:  
 
The objective of the Controlling a Stage process is to ensure that:  
  
Line 46: Line 48:
 
* Take corrective action – Solve issues while keeping stage within tolerance.
 
* Take corrective action – Solve issues while keeping stage within tolerance.
  
[[File:Slide84.PNG|900px]]
+
[[File:Slide84.PNG|800px|alt=Controlling a Stage]]
  
 
== Inputs ==
 
== Inputs ==
Line 53: Line 55:
 
The main inputs are the [[Stage Plan]] and information in the [[Project Initiation Documentation]].
 
The main inputs are the [[Stage Plan]] and information in the [[Project Initiation Documentation]].
  
[[File:CS-InOut.png|890px]]
+
[[File:CS-InOut.png|800px|alt=Controlling a Stage]]
  
 
== Outputs ==
 
== Outputs ==
Line 77: Line 79:
 
== Reference ==
 
== Reference ==
  
* [http://mplaza.pm/product/prince2-foundation-pdf-training-manual/ The PRINCE2 Foundation Training Manual], by Frank Turley
+
'''PRINCE2 Courses'''
* [http://prince2.center/ Compare all PRINCE2 online Foundation courses]
+
* [https://www.mplaza.training/online-courses/prince2-foundation/?CP=q2yenF02 PRINCE2 Foundation online training course] 
 +
* [https://www.mplaza.training/online-courses/prince2-practitioner/?CP=q2yenF02 PRINCE2 Practitioner online training course]
 +
* [https://www.mplaza.training/online-courses/prince2-agile-practitioner/?CP=q2yenF02 PRINCE2 Agile online training course] <BR>
 +
 
 +
'''PRINCE2 Exams'''
 +
* [https://www.mplaza.training/official-exams/prince2-foundation/?CP=q2yenF02 PRINCE2 Foundation Exam]  
 +
* [https://www.mplaza.training/official-exams/prince2-practitioner/?CP=q2yenF02 PRINCE2 Practitioner Exam]   
 +
* [https://www.mplaza.training/official-exams/prince2-agile-practitioner/?CP=q2yenF02 PRINCE2 Agile Practitioner Exam]  <BR>
 +
 
 +
'''Other PRINCE2 Links'''
 +
* [https://unbored.training/courses/prince2-foundation-exam-simulator/?CP=q2yenF02 PRINCE2 Foundation Exam Simulator]
 +
* [https://mplaza.training/awareness-courses/?CP=q2yenF02 Email awareness courses (PRINCE2, PMP, Scrum, Agile)]
 +
* [http://prince2.center/ PRINCE2 online]  - Compare all PRINCE2 online Foundation courses <BR> <BR>
 +
 
  
 
[[Category:Processes]]
 
[[Category:Processes]]
 +
 +
 +
PRINCE2® is a registered trade mark of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved.

Latest revision as of 12:02, 1 June 2019

This article is also available in Italian, Spanish, Portuguese, French, Russian.


Purpose

The purpose of the Controlling a Stage process (CS) is for the Project Manager to assign the work to be done, monitor this work, deal with issues, report progress to the Project Board and take corrective action to ensure that the stage remains within tolerance.


Objective

The objective of the Controlling a Stage process is to ensure that:

  • Attention is focused on the delivery of the products.
  • Keep Risks and Issues under control.
  • Keep the Business Case under review.
  • Deliver the products for the stage to the agreed quality within agreed cost and time and achieve the defined benefits.

Context

The Controlling a Stage process describes the work of the Project Manager as they do their day-to-day management of a stage, and it is where the Project Manager does most of their work.

During a stage the Project Manager will repeat the following tasks:

  • Authorize the work to be done (give out work in Work Packages to the Team Managers).
  • Monitor progress information for this work using Checkpoint Reports and Quality Register.
  • Review the current situation in relation to the Stage Plan, sign off completed work and issue new Work Packages.
  • Report to the Project Board using the Highlight Report.
  • Watch for issues, assess issues and deal with issues and risks.
  • Take any necessary corrective action.

As mentioned above, the Project Manager will keep repeating these tasks until all the planned products for the stage have been completed and then start to prepare for the Managing a Stage Boundary process. This whole sequence of activities is again repeated for each stage in the project.

At the end of the last stage, the Closing a Project process will be invoked and therefore, the Project Manager will start to prepare the project for closure.

Activities

  • Authorize a Work Package – Assign and agree with the Team Manager.
  • Review Work Package Status – Check on Work Package progress.
  • Receive completed Work Package – Check quality and Configuration Management.
  • Review the stage status – Continually compare status to Stage Plan.
  • Report Highlights – Regular reports to the Project Board.
  • Capture and examine issues & risks – Categorizing and assess impact.
  • Escalate issues and risks – Create Exception Report and send to the Project Board.
  • Take corrective action – Solve issues while keeping stage within tolerance.

Controlling a Stage

Inputs

The trigger to start each CS process is the Authorization from the Project Board. The main inputs are the Stage Plan and information in the Project Initiation Documentation.

Controlling a Stage

Outputs

  • Highlight Reports are used to keep the Project Board up to date on the stage progress.
  • The Project Manager constantly reviews Issues, Risk and Quality and therefore updates the Issue, Risk and Quality registers.
  • Issue Reports (includes Change Requests) are used to escalate issues to the Project Board.
  • Exception Reports are used to report if the stage is out of tolerance or is forecast to be.
  • The Stage Boundary process commences near the end of the current stage.

Roles and Responsibilities

Reference

PRINCE2 Courses

PRINCE2 Exams

Other PRINCE2 Links


PRINCE2® is a registered trade mark of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved.