兑而成,具有酱香突出、甘润爽口、回.pptVIP

* WBS development is part science, part art. No WBS is entirely right, or entirely wrong. There are many measures of “goodness” and maximizing one measure might diminish another. (Example: more detail in the WBS to increase “understanding and communication” means the WBS is bulkier and more difficult to maintain.) (Example: Should you associate training with each lower-level element, or put it all under one element at level 1?) The above list will help you maximize the WBS’s overall goodness. Divisions that minimize interfaces and are stand-alone testable may not be obvious; requires thought to come up with it. Note guideline to associate imbedded software with its hardware. The test “Eliminating one product….costs” is important when using automated cost estimating software such as Microframe Program Manager. The ultimate measure: is the WBS useful? Also: any topic that is a real “lightening rod” in the organization should be visible at a high level. Example: safety, if on an earlier project someone was hurt. Example: if customers had complained about lack of adequate training in the past. Pass out extracts from MIL-HDBK-881 Work Breakdown Structure Handbook. Note it’s available on website in reference. Note the WBS Dictionary included therein; articulates what’s included and also what’s intended to be excluded. * ANIMATED Contrast tree to indented list (outline). One manager (Warren Dunham) had this insight: The top 3 levels are of interest and concern to the funders. Whereas the actual worker’s concerns begin at level 5. Hard to bridge that gap between level 3 and 5! You can draw tree with PowerPoint org chart function. Graphic tree structure is good for high-level briefing. You are forced to use the indented list view when you do a cost estimate, because tools (e.g. Excel) utilize that view. * Scenario: a new person to company has a great idea for a new product. You need to develop a WBS for this project, so that you can present it to the company pre