Can't find what your looking for?

Call us on +44 (0)1273 622272 or contact us.

Courses

showing {{courseLimit}} of {{(courses | filter:query).length}} results Show All

Hide All

Categories

showing {{courseLimit}} of {{(tags | filter:query).length}} results Show All

Hide All

theBLOG

Download PRINCE2 Project Templates

Written by Andy Trainer – Wed 18 Nov 2009

PRINCE2 Project Templates DownloadIf you've attended our PRINCE2® Foundation or PRINCE2 Practitioner course and want to start a project using PRINCE2 back at work, you'll need somewhere to start.

Here you can download official PRINCE2 project templates to help you to manage your project effectively.

You can download a zipped folder containing all of the PRINCE2 project templates or select individual templates from the list below:

PRINCE2 Project Templates:

Read More


Managing Product Delivery (MP) PROCESS

Written by Andy Trainer – Wed 11 Jul 2007

PRINCE2® PROCESSES – Managing Product Delivery (MP)

Managing Product Delivery Process Diagram

The purpose of the Managing Product Delivery process is to control the link between the Project Manager and the Team Manager(s), by placing formal requirements on accepting, executing and delivering project work.

The role of the Team Manager(s) is to coordinate an area of work that will deliver one or more of the project’s products. They can be internal or external to the customer’s organization.

The objective of the Managing Product Delivery process is to ensure that:

  • Work on products allocated to the team is authorized and agreed.
  • Team Managers, team members and suppliers are clear as to what is to be produced and what is the expected effort, cost or timescales.
  • The planned products are delivered to expectations and within tolerance.
  • Accurate progress information is provided to the Project Manager at an agreed frequency to ensure that expectations are managed.

Products that are created or updated during this process are:

  • Team plans with actual dates.
  • Risk register with any identified work package level risks.
  • Quality register with all quality work that is being undertaken.
  • Configuration Item Records with the latest status of products produced.
  • Project Issues with status information and impact analysis for current or new issues identified.
  • Checkpoint Reports providing regular progress information to the Project Manager.

Silicon Beach Training is an accredited training organisation for PRINCE2 Training.

Read More


Controlling a Stage (CS) PROCESS

Written by Andy Trainer – Wed 11 Jul 2007

PRINCE2® PROCESSES – Controlling a Stage (CS)

Controlling a Stage Diagram

The purpose of the Controlling a Stage process is to assign work to be done, monitor such work, deal with issues, report progress to the Project Board, and take corrective actions to ensure that the stage remains within tolerance.

For each stage, the following cycle of activities will be covered:

  • Authorise a Work Package
  • Review Work Package Status
  • Receive Completed Work Packages
  • Review the stage status
  • Report highlights
  • Capture and examine issues and risks
  • Escalate issues and risks
  • Take correction action

The continued assessment of risk and issues during this process is important.

Products used or produced during this process:

  • Work packages, detailing the products to be produced must be agreed between Project and Team Manager.
  • Quality register – checked for approved products produced
  • Configuration item records – updated with latest status of products
  • Checkpoint reports – reviewed in preparation for Highlight reports
  • Highlight Reports (time driven control) produced by the Project Manager, sent to the Project Board advising on progress information.
  • Issue reports and Issues register in which all issues are captured and examined.
  • Daily log – used to informally manage any risks and issues
  • Lessons log – updated with any lessons learned during the stage
  • Updated Risk register.
  • The Stage Plan which is regularly updated with actual achievements.
  • An Exception Report may also need to be created if an issue is forecast to exceed stage tolerances.

Learn more about the Controlling a Stage Process on our PRINCE2 Courses.

Read More


Initiating a Project (IP) PROCESS

Written by Andy Trainer – Wed 11 Jul 2007

PRINCE2® PROCESSES – Initiating a Project (IP)

Initiating a Project Process

See our training for PRINCE2.

The purpose of the Initiating a Project process is to establish solid foundations for the project, enabling the organisation to understand the work that needs to be done to deliver the project’s products before committing to a significant spend.

The objective of the Initiating a Project process is to ensure that there is a common understanding of:

  • The reasons for doing the project, the benefits expected and the associated risks
  • The scope of what is to be done and the products to be delivered
  • How and when the project’s products will be delivered and at what cost
  • Who is to be involved in the project decision making
  • How the quality required will be achieved
  • How baselines will be established and controlled
  • How risks, issues and changes will be identified, assessed and controlled
  • How progress will be monitored and controlled
  • Who needs information, in what format, and at what time

Other products created and ready for use when the project commences are:

  • Risk Management Strategy and Risk Register
  • Configuration Management Strategy, Initial Configuration Item Records and Issue Register
  • Quality Management Strategy and Quality Register
  • Communication Management Strategy
  • Project Controls
  • Role Descriptions
  • Project Management Team Structure
  • Project Plan
  • Product Descriptions
  • Benefits Review Plan
  • Detailed Business Case
  • Project Initiation Documentation

Read More