Use the Product Breakdown Structure (PBS) to visualise all the components that make up the product
The Product Breakdown Structure (PBS) is a communication & planning tool. The Product Breakdown Structure is an excellent way to visualise what is needed for the end product without going into too much detail. As it is a diagram you can use it to communicate across language barriers. When used in conjunction with the “Product Description” you have a powerful means of communicating what the project is expected to deliver. This can be used for guiding the teams in defining the detailed requirements.
Creating the Product Breakdown Structure is an iterative process
The process of breaking down the end product into its component parts is iterative and works in conjunction with developing the component product descriptions, the Product Flow Chart (also known as the Build Road Map) and the User Scenarios and Acceptance Tests.
If the term “Product” is a little confusing then substitute it with a term relevant to what your are doing. A person working on an ERP system may substitute “Product” with “ERP System”. A person building a hotel may use the term “Hotel Complex”.
For those working with Agile software development the “Component Product” is the same as an “Epic”
What does a well-formed Product Breakdown Structure do?
What can we use a well-formed Product Breakdown Structure for?
Generic Product Breakdown Structure can be used to improve planning and communication
E-Commerce Product Breakdown Structure can be used to improve planning and communication