PURPOSE, OBJECTIVES and RELATIONSHIP WITH THEMES
PRINCE2® 2017 PROCESSES yellowhouse.net
Purpose of Starting up a Project (SU)
To ensure prerequisites for Initiating a Project are in place • Do we have a viable and worthwhile project?
To do the minimum necessary to decide if it is worthwhile to initiate a project
To prevent poorly conceived projects from being initiated
SU is a pre-project process
The PRINCE2ÂŽ Accredited Training Organization logo \is a trade mark of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved. Yellowhouse is an AXELOS Accredited Training Organization (ATO)
Objectives of Starting Up a Project
Business justification
Necessary authorities
Sufficient information is sought to define and confirm the scope of the project
The project approach is selected
Individuals are appointed for the Initiation Stage
The work of Initiation is planned
Time is not wasted on Initiation if there aren’t sufficient grounds to proceed
Relationship between Starting up a Project and the Themes
Plans Progress Organization Quality Business Case
Purpose of Directing a Project (DP)
• To enable the Project Board to be accountable for the project’s success by • Making key decisions • Exercising overall control • Delegating day-to-day management of the project to the Project Manager on a stage by stage basis • Starts after SU
Objective s of Directing a Project
Authority to initiate the project
Authority to deliver the project’s products
Provision for management direction and control
Corporate or programme management interface to the project
Authority to close the project
Plans for realizing post-project benefits
Relationship between Directing a Project and the Themes
Change Plans Progress Risk Organization Quality Business Case
To establish solid foundations for the project
Purpose of Initiating a Project
To enable the organization to understand the work to be done to deliver the project’s products
Before committing to a significant spend (financial investment)
Objectives of IP
• To ensure a common understanding of: • The reasons for the project, benefits expected and associated risks • Quality requirements • Who is to be involved • What is to be done (scope) • When things will get done • How progress will be monitored and controlled • Communication requirements • How the project management method will be tailored
Relationship between Initiating a Project and the Themes Change Plans
Risk
Organization Quality Business Case
To assign work to be done
Purpose of Controllin g a Stage
To monitor the work To deal with issues To report progress to the Project Board To take corrective action to ensure the stage remains within tolerance
Objective s of Controllin g a Stage
1
2
Attention is focused on delivery of the stage’s products
Risks and issues are kept under control
3 The Business Case is kept under review
4
5
The agreed products for the stage are delivered within the required constraints
The project management team is focused on delivery within the tolerances
Relationship between Controlling a Stage and the Themes
Change Plans
Progress Risk Organization Quality
Purpose of Managing Product Delivery
01
02
03
To control the link between the Project Manager and the Team Manager(s) by placing formal requirements on
The role of the Team Manager is to coordinate an area of work
The Team Manager can come from the customer’s organization or could be from an external party
• Accepting, executing and delivering project work
• To deliver one or more of the project’s products
Objective s of Managing Product Delivery
Work on products allocated to the team is authorized and agreed
Team Managers, team members and suppliers are clear about what is to be produced
The planned products are delivered to requirements/tolerance
Accurate progress information is provided to the Project Manager
Relationship between Managing Product Delivery and the Themes
Change Plans Progress Risk Quality
Purpose of Managing a Stage Boundary
To enable the Project Board to have enough information from the Project Manager so it can
Projects do not always go to plan so the Project Board may also need to
Review the success of the current stage
Approve an Exception Plan
Approve the next Stage Plan
Review the updated Project Plan
Confirm continued business justification and acceptability of the risks
Objective s of Managing a Stage Boundary
Assure
Assure the Project Board that all products in the Stage Plan for the current stage have been completed and approved
Prepare
Prepare the Stage Plan for the next stage
Review and update
Review and update (if necessary) the PID
Provide
Provide information necessary for the Board to assess the project’s ongoing viability
Record
Record any information or lessons for later stages
Request
Request authorization for the next stage
Relationship between Managing a Stage Boundary and the Themes
Plans Progress Risk Organization Quality Business Case
Purpose of Closing a Project
To provide a fixed point at which acceptance for the project product is confirmed
It supports the Principle of • Learn from experience
To recognise that objectives set out in the original PID have been achieved or that the project has nothing more to contribute
Objective s of Closing a Project
Verify user acceptance of the project’s products
Ensure that the host site is able to support the products on project closure
Review project performance against baselines
Assess benefits already realized
Deal with on-going issues and risks through follow-on action recommendations
To recognize whether or not objectives set out in the original PID have been achieved
Relationship between Closing a Project and the Themes Plans Progress Risk Organization Quality Business Case
Processes
Themes
Relationship between the Processes and the Themes Starting up a Project Directing a Project Initiating a Project Controlling a Stage Managing Product Delivery Managing a Stage Boundary Closing a Project
Change
Plans
Progress
Risk
Organization
Quality
Business Case
ANOTHER LIZZIELALA PRODUCTION from yellowhouse.net