Talk:Product breakdown structure

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

PBS vs WBS[edit]

I removed the following example as it is a work breakdown structure (WBS) and not a PBS.

WBS of a baking a cake:

  • Gather recipy
    • Gather ingredients
      • Mix ingredient
    • Gather tools
      • Mix
      • Put it in a
      • Bake Cake

Everything in the example above is about activities in baking a cake. An example of PBS of a cake:

  • Cake
    • Icing
      • List of ingredients...
    • Sponge base
      • List of ingredients...
    • Cake box

Rellis1067 10:21, 4 September 2005 (UTC)Reply[reply]

A product breakdown structure has a far wider application then just defining a project deliverable.

It is used in (for example) systems engineering in conjunction with a functional breakdown, your off-the-shelf car maintenance manual to illustrate the bits that make up the engine and where they fit into higher-level assemblies (an illustrated parts breakdown IPB), and MIL-STD-13882B compliant databases for military logistics support.

And I'm not sure how the reference to Prince2 adds to the definition of product breakdown structure.


Outdated example[edit]

The example of the computer is seems increasingly archaic (how many computer displays now include a cathode ray tube?) — Preceding unsigned comment added by (talk) 22:09, 24 June 2012 (UTC)Reply[reply]

I agree - the PC example is outdated. Also it is weird that CPU & RAM go under motherboard. They are connected, but not subcomponents of the motherboard. Also the mouse with a ball could be something that the younger generation may not understand. — Preceding unsigned comment added by (talk) 08:55, 9 June 2015 (UTC)Reply[reply]

Agreed as well, and without a clear description of the project's purpose, I think this antiquated example doesn't contribute to understanding. I propose deleting it. "Six by nine. Forty two." (talk) 16:56, 6 December 2021 (UTC)Reply[reply]