Product Breakdown Structure 1.0.0

Scope

This document registers all elements forming the systems to be produced. Therefore, each product has to be manageable from these viewpoints:

1. Configuration Item (storing and retrieving/distributing)
2. Quality management (being up to the specific requirements)
3. Production (being sure that all the properties are compatible with other elements)
4. Trading (its intrinsic cost and value within a time-frame)

Quality

The effectiveness can be measured with these parameters:

1. Accuracy. All information is linked to its sources and links are probed.
2. Timeliness. The baseline is set contextually with the Integrated Main Plan and Schedule.
3. Clarity. Beside the indication of the actual scope, a brief explanation has to be integrated with specific references (verifying that those documents were updated and accessible to the reader)
4. The following checks need to be strictly integrated with the existing documentation both on product and on plan – especially resources (skills, availability, costs).

Process

The addition of new elements starts with the Product Description (Architectural Document) and then a new layer of elements will be added for each session of planning at stage-level.

This document collects all the planned and the produced elements for tracking their property. Therefore, any reference to the existing and future elements has to be clear, unique and regularly updated in all its aspects as described in the “Registrar Section”.

RACI (who does what)

Operation desc./Roles[1]	Spr	PM	SME	BA /TL	Stkhd
“Configuring “the register on the basis supplied by the Architectural document.	I	A	C	R	C
Verifying that all necessary information is consisted with the Quality  Management Strategy and all the tools to be used for managing such information.	I	R	C	R	C
Approving	C	A	C	R	C
Updating whenever the is required	A	R	I	I	C

Document structure

Distribution list

This kind of information are fundamental for everyone is involved in the specific production’s area. However, some data can be considered sensitive. Therefore, it depends upon the implemented “profiling policy” as described in the “Communication Management Strategy”.

Registrar section

These are the key fields

Product element ID	Unique identifier
Title	Name by which the product is known
Purpose	This defines the purpose that the product will fulfil within the system and then in the output.
Composition	Any meaningful reference to the elements/sub-systems forming it. This information is essential for understanding the relationship (especially dependencies) with other products
Derivation	What are the source products from which this product is derived? All references have to be documented with specific links
Producer	People involved in the process. It is important to define the main role and the subsequent actors. Any chance in the “ownership” are potential source of risks.
Quality method	Which is/are the methods (listed in the QSM) to be used for verifying its compliance to the standards?
Quality tolerance	As stated in the QMS
Approved by	Project Manager

Technical domains

1. Integrated Master Plan / Schedule
2. Stage / Work-package plan
3. Product Description
4. Quality management strategy
5. Resource allocation plans

Financial / Commercial domains

1. Suppliers’ contracts

2)    Customer’s contracts

---

[1] Spr Sponsor, PM Project manager, BA Business Analyst, TL Technical Leader, Prd Producer, Stkhd Stakeholder