Plans

• Purpose
• Defined
  • What is a plan?
  • What is planning?
  • Levels of plan
  • The Project Plan
  • Stage Plans
  • Team Plans
  • Exception Plans
• The PRINCE2 approach
  • Philosophy
  • Prerequisites for planning -
    design the plan
  • Define and analyse the products
• Prerequisites for planning
  • Write the Project Product Description
  • Create the product breakdown structure
  • Write the Product Descriptions
  • Create the product flow diagram
• Identify activities and dependencies
  • Activities
  • Dependencies
• Prepare estimates
• Prepare the schedule
  • Overview
  • Define activity sequence
  • Assess resource availability
  • Assign resources
  • Level resource usage
  • Agree control points
  • Define milestones
  • Calculate total resource requirements and costs
• Analyse the risks
• Document the plan
• Responsibilities

Key sections

• Introduction
• Business case
• Organization
• Quality
• Plans
• Risk
• Change
• Progress
• Introduction to processes
• Starting up a projectDirecting a project
• Initiating a project
• Controlling a stage
• Managing Product Delivery
• Managing a Stage Boundary
• Closing a Project
• Tailoring PRINCE2 to the project environment
• Directing Projects with PRINCE2

The PRINCE2 approach

© Crown copyright 2005 Reproduced under licence from OGC

Philosophy

The philosophy behind producing plans in PRINCE2® is that the products required are identified first, and only then are the activities, dependencies and resources required to deliver those products identified.

This is known as product-based planning and is used for the Project Plan, the Stage Plan and, optionally, the Team Plan.
The diagram illustrates the steps required in producing a PRINCE2 plan.

Each step in the planning procedure may need to be revisited on completion of later steps (for example, in preparing the schedule if additional activities or dependencies are identified).

PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.