It is a technique that can be used as part of many processes, for example, the sub-process Defining and Analysing Products (PL2).
It provides a simple method for devising the project’s work in order to produce a product.
In this case, a ‘product’ can be many things, for example, a piece of equipment or a document, which are tangible items.
Alternatively, it may be intangible, such as, a culture change or organisational restructuring.
The technique will create 4 products:
It ensures that all breakdowns and activities that lead to the final product add value
This breaks down the final product into all of its sub-products in a hierarchical order.
It will help to assess all of the work required to complete the final product.
Doing this will improve the efficiency of estimation of effort, resource and timescale needed.
It will apply quality more specifically and will reduce the possibility of omitting products.
They help the project by defining exactly what is required for each product and as such will help to identify those activities required to produce each product. The Product Description reflects the quality standard required for the product. It will be used by testers at a later stage to help verify the necessary quality has been achieved.
How many Product Descriptions will you need?
It will depend on just what level you wish to go down to.
There must be at least one for the final product.
In addition, you should choose relevant products from the Product Breakdown Structure.
Product Descriptions help everyone understand the nature and purpose of the product with no ambiguity.
In addition, they will identify the necessary quality criteria and the testing methodology.
It will naturally develop from the Product Breakdown Structure and represents the ‘flow’ of activities, together with any dependencies between them.
This will lead to network planning and Gantt charts that represent the project schedule.
The first task in product-based planning is to sit down with the Customer and write a Product Description of the final product.
There is a list of requirements for a Product Description in the file ‘Product description.doc’ which is part of the product package.
The second task is to product the Product Breakdown Structure.
Before you can do this you must: