Premium
Product‐Only WBS
Author(s) -
Grady Jeffrey O.
Publication year - 1997
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1997.tb02216.x
Subject(s) - work breakdown structure , context (archaeology) , computer science , product (mathematics) , process (computing) , new product development , systems engineering , work (physics) , process management , project planning , engineering management , project management , engineering , project charter , business , programming language , mathematics , mechanical engineering , paleontology , geometry , marketing , biology
DoD has traditionally required a work breakdown structure (WBS) on programs that includes both product and services components apparently based on the belief that this is the only way to account for all program cost elements. The author maintains, and supports in this paper, that not only is it possible to capture all program work under a product‐only WBS but that it will encourage better program planning, more manageable programs, and a more efficient transform between an enterprise identity and the needs of all programs within the enterprise. The author extends the U.S. Air Force integrated management system beyond the notions advanced in his book System Engineering Planning and Enterprise Identity involving the generic to program planning transform. This transform is made simpler and easier to apply within the context of a product‐only WBS. We begin by reviewing the purposes of the two axes of the matrix management structure. The functional organization is the key to written practices, personnel training, continuous improvement, and an efficient program planning process. We will then defend the product‐only WBS and discuss how the program planning transform process can be implemented within the context of the product‐only WBS.