Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Product breakdown structure
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Other uses of|breakdown structures|Breakdown structure (disambiguation){{!}}Breakdown structure}} {{short description|Tool for analysing, documenting and communicating the outcomes of a project}} {{more citations needed|date=January 2021}} In [[project management]] under the [[PRINCE2]] methodology, a '''product breakdown structure''' ('''PBS''') is a tool for analysing, documenting and communicating the outcomes of a project, and forms part of the [[product based planning]] technique. The PBS provides "an exhaustive, hierarchical [[tree structure]] of [[deliverable]]s that make up the project, arranged in whole-part relationship" (Haughey, 2015).<ref>Duncan Haughey. (2015) ‘Project Management Tools’, Project Smart. Available from: https://www.projectsmart.co.uk/project-management-tools.php</ref> ==Comparison with the work breakdown structure== The PBS is identical in format to the [[work breakdown structure]] (WBS), but is a separate entity and is used at a different step in the planning process. The PBS precedes the WBS and focuses on cataloguing all the desired outputs (products) needed to achieve the goal of the project. This feeds into creation of the WBS, which identifies the tasks and activities required to deliver those outputs. Supporters of product based planning suggest that this overcomes difficulties that arise from assumptions about what to do and how to do it by focusing instead on the goals and objectives of the project – an oft-quoted analogy is that "PBS defines where you want to go, the WBS tells you how to get there". ==Example== [[File:Product Breakdown Structure example.gif|thumb|right|410px|Example of a product breakdown structure of a [[computer]].]] The diagrammatic representation of project outputs shown provides an example of a clear and unambiguous statement of what the project is to deliver. PBS of a computer (see image on right): * Main unit ** Housing ** Motherboard *** CPU *** RAM chips *** ... ** Hard disk drive ** Graphics card ** Sound card ** Network card * Monitor ** Display ** Housing ** Electronic components * Mouse ** Body ** Optical sensor ** Battery * Keyboard ** Keys == See also == * [[List of project management topics]] * [[Product (business)]] * [[Product description]] * [[Product management]] * [[Project management]] * [[Work breakdown structure]] * [[Value breakdown structure]] * [[Product flow diagram]] == References == <references /> == Further reading == * A Framework for Software Product Line Practice [http://www.sei.cmu.edu/productlines/frame_report/glossary.htm Glossary] * [http://prince2.wiki/Plans#PBP_Step_2:_Create_the_Product_Breakdown_Structure Product Breakdown Structure at PRINCE2 wiki] [[Category:Project management techniques]] [[Category:Product management]] [[Category:PRINCE2]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:More citations needed
(
edit
)
Template:Other uses of
(
edit
)
Template:Short description
(
edit
)