Created/updated 15/04/21© Crown copyright 2009.PRINCE2™ is a Trade Mark of the Office of Government Commercepage 1 of 6PRINCE2™- Plan Project Name:Date:Release:Draft/FinalAuthor:Owner:Client:Document Number: Note: This document is only valid on the day it was printedRevision HistoryDate of next revision: Revision DatePreviousRevision DateSummary of ChangesChangesMarked ApprovalsThis document requires the following approvals. A signed copy should be placed in the project files. NameSignatureTitleDate of IssueVersion DistributionThis document has been distributed to: NameTitleDate of IssueVersion Plan Created/updated 15/04/21© Crown copyright 2009.PRINCE2™ is a Trade Mark of the Office of Government Commercepage 2 of 6Overview PurposeA plan provides a statement of how and when objectives are to beachieved, by showing the major products, activities and resources required for the scope of the plan. In PRINCE2, there are three levels of plan: project,stage and team. Team Plans are optional and may not need to follow thesame composition as a Project Plan or Stage Plan.An Exception Plan is created at the same level as the plan that it isreplacing.A Project Plan provides the Business Case with planned costs, and itidentifies the management stages and other major control points. It is usedby the Project Board as a baseline against which to monitor projectprogress.Stage Plans cover the products, resources, activities and controls specific tothe stage and are used as a baseline against which to monitor stageprogress.Team Plans (if used) could comprise just a schedule appended to the WorkPackage(s) assigned to the Team Manager.A plan should cover not just the activities to create products but also theactivities to manage product creation – including activities for assurance,quality management, risk management, configuration management,communication and any other project controls required.Contents The Plan should cover the following topics.Plan Description ……………………………………………………………………………………..4Plan Prerequisites …………………………………………………………………………………..4External Dependencies……………………………………………………………………………4Planning Assumptions……………………………………………………………………………..4Lessons Incorporated……………………………………………………………………………..4Monitoring and Control…………………………………………………………………………..5Budgets…………………………………………………………………………………………………5Tolerances…………………………………………………………………………………………….5Product Descriptions ……………………………………………………………………………….5Schedule……………………………………………………………………………………………….6Advice The Plan is derived from the Project Brief, Quality Management Strategy (forquality management activities to be included in the plan), Risk ManagementStrategy (for risk management activities to be included in the plan),Communication Management Strategy (for communication managementactivities to be included in the plan), Configuration Management Strategy(for configuration management activities to be included in the plan),Resource availability, and Registers and logs.The Plan can take a number of formats including: A stand-alone document ora section of the Project Initiation Documentation; Document, spreadsheet,presentation slides or mindmap; Entry in a project management tool.The schedule may be in the form of a product checklist (which is a list ofthe products to be delivered within the scope of the plan, together withkey status dates such as draft ready, quality inspected, approved etc.) orthe output from a project planning tool.Plan Created/updated 15/04/21© Crown copyright 2009.PRINCE2™ is a Trade Mark of the Office of Government Commercepage 3 of 6The following quality criteria should be observed:• The plan is achievable• Estimates are based on consultation with the resources, who willundertake the work, and/or historical data• Team Managers agree that their part of the plan is achievable• It is planned to an appropriate level of detail (not too much, not toolittle)• The plan conforms to required corporate or programme standards• The plan incorporates lessons from previous projects• The plan incorporates any legal requirements• The Plan covers management and control activities (such as quality) aswell as the activities to create the products in scope• The plan supports the Quality Management Strategy,Configuration Management Strategy, Risk Management Strategy,Communication Management Strategy and project approach• The plan supports the management controls defined in the ProjectInitiation DocumentationPlan Created/updated 15/04/21© Crown copyright 2009.PRINCE2™ is a Trade Mark of the Office of Government Commercepage 4 of 6Plan Description(Covering a brief description of what the plan encompasses (i.e. project, stage, team,exception) and the planning approach)Plan Prerequisites(Containing any fundamental aspects that must be in place, and remain in place, for theplan to succeed)External Dependencies(That may influence the plan)Planning Assumptions(Upon which the plan is based)Lessons Incorporated(Details of relevant lessons from previous similar projects, which have been reviewed andPlan Created/updated 15/04/21© Crown copyright 2009.PRINCE2™ is a Trade Mark of the Office of Government Commercepage 5 of 6accommodated within this plan)Monitoring and Control(Details of how the plan will be monitored and controlled)Budgets(Covering time and cost, including provisions for risks and changes)Tolerances(Time, cost and scope tolerances for the level of plan (which may also include morespecific stage- or team-level risk tolerances))Product Descriptions(Covering the products within the scope of the plan (for the Project Plan thiswill include the project’s product; for the Stage Plan this will be the stageproducts; and for a Team Plan this should be a reference to the Work Packageassigned). Quality tolerances will be defined in each Product Description)Plan Created/updated 15/04/21© Crown copyright 2009.PRINCE2™ is a Trade Mark of the Office of Government Commercepage 6 of 6ScheduleThis may include or reference graphical representations of the following:• Gantt or bar chart • Activity Network• Product breakdown structure • Table of resource requirements – by resource type (e.g. fourengineers, one test manager, one business analyst)• Product flow diagram • Table of requested/assigned specific resources –by name (e.g. Nikki,Jay, Francesca)The Schedule may also be in the form of a Product Checklist as shown below ProductIdentifierProduct TitleProductDescriptionapprovedDraft ReadyFinal QualityCheck completedApprovedHanded Over (ifapplicable)PlanActualPlanActualPlanActualPlanActualPlanActual
