By defining a plan in terms of the products to be delivered, the creation, quality and suitability of those products can be managed and controlled more easily. In addition, by defining the required products, everyone involved can see and understand the required outcome.
Once the decisions on the approach to planning have been made in Designing a Plan (PL1), this sub-process will be the normal starting point for producing the plan.
This sub-process is divided into three steps:
These steps are described in more detail in Product-based planning().Product Checklist
A draft of the Product Checklist can be created at this time from the information in the Product Breakdown Structure.
The Product Description is given in file ‘product checklist.doc’ in the product package.
It shows all the products of the plan with entries for the planned and actual dates when the product reaches key moments in its creation, such as ‘Draft Ready’, ‘Quality Check Done’ and ‘Product Approved’.
These are suggested events and can be varied according to the needs of the project.
The planned dates are added at the end of planning (PL) after scheduling and any adjustments for risk actions.
The Project Manager adds the actual dates as they are achieved and this can form a useful addition to the Highlight Report.
Use of the Product Checklist is optional in a project.
The Project Manager is responsible for the sub-process for Project and Stage Plans, Team Plans may well be produced by Team Managers for agreement by the Project Manager. There should be consultation with the customer, user(s) and specialists to ensure that all the required products are covered.
Those with Project Assurance responsibilities should vet the results.
The Configuration Librarian is responsible for the creation of Configuration Item Records for all necessary products, as specified in the Configuration Management Plan.
|Plan design||Input||This defines the level of plan required, the tools and estimating techniques to be used, and the approach to change and contingency allowance.|
|Project Quality Plan||Input||This will guide the selection and placement of quality control activities. Also contains the Configuration Management Plan. This will identify products which will require Configuration Item Record.|
|Product Breakdown Structure||Output||A hierarchical table of all the products required to be created in the plan.|
|Product Description / Configuration Item Records||Output||A description of each product plus its quality criteria. This is also the initial creation of the Configuration Item Records for the products.|
|Product Checklist||Output||(If used) A draft list of the major products of the plan.|
|Product Flow Diagram||Output||A diagram showing the sequence in which the products should be produced.|
These are given in tabular form in the file ‘PL2 defining and analysing products.doc’ in the product package.
A decision point can be associated with one or more intermediate products on which the decision will be based.
The list of products, their required sequence and their descriptions should all be quality reviewed for accuracy and completeness.
Required quality is a criterion against which the product will be accepted.
When working in a customer / supplier relationship, this may form the basis of project acceptance.
The definition of the major end products or results required to satisfy the business needs should be documented within the Project Initiation Document as part of the project objectives.