Unit 06 Developing the Work Breakdown Structure

Transcription

1 Unit 06 Developing the Work Breakdown Structure April 2007 Project Management Wilhelm F. Neuhäuser IBM Corporation 2007

2 Agenda Unit 6: Developing the Work Breakdown Structure Objectives Value of the WBS WBS definitions WBS development process Uses of the WBS Key Messages - Unit 6 2

3 Objectives At the end of this module, you will be able to - Develop a WBS for a project Define the WBS dictionary Decribe the importance and uses of the WBS for managing a project Distinguish between cost accounts and work packages 3

4 WBS - Work Breakdown Structure Dominant prerequisite for successfully integrating and controlling the total project Framework on which a project is built and the "map" for executing the project Graphically depicts the hierarchy of the project 4

5 Benefits of Using a WBS Provides the framework to identify development projects separately from geographies, accounting systems, funding sources, and so on Clarifies responsibilities Focuses attention on project objectives Encourages detailed planning and documentation Identifies specific work packages for estimating and assigning work 5

6 WBS Definitions WBS - A task- or product-oriented family-tree division of hardware, software, services, data, and other work tasks that completely define the project 1.0 XYZ Product Development 1.1 Develop Product Requirements and Concepts Receive concept for new products Form product development team Indentify members Schedule kickoff meeting Conduct meeting Develop initial product proposal and plan 1.1 Develop product reqrmt & concept XYZ Product Development Develop & verify product 1.3 Ramp-up and launch product -- Cost account level -- Work package level Size and number of WBS levels vary with project, but the WBS must be complete to relate all elements to one another and to the total product. 6

7 WBS Definitions (continued) Cost account One level above the work package where costs are accrued - lowest management and control level Work package Lowest level of the WBS consisting of required tasks to complete each product - used to budget and schedule with a defined delivery date Rule of Thumb: Work package should consist of approximately 80 hours of labor effort (PMI standard) 7

8 WBS Development Process 1. Develop and/or review project goals and objectives 2. Prepare a summary (high-level) WBS Total project: Level 1 Major subsystem and project services: Level 2 Major subsystems and project services elements: Level 3 3. Meet with responsible project team members, sponsors, and other project stakeholders (internal and external) 8

9 WBS Development Process (continued) 4. Responsible departments and geographies further define to lowest meaningful level, which produces work packages, including - Technical performance parameters Schedule (with a defined delivery date) Expenses 5. Prepare detailed WBS dictionairy 9

10 WBS Dictionary WBS dictionary must include Work item number Work item title Description of work Predecessors and successors Work to be accomplished Deliverable/objective How do you know you are done? Who needs the output? Ownership/participation Who is responsible? Who else will be involved? 10

11 Uses of the WBS Planning and budgeting Funding Estimating Scheduling Performance measurement Change management 11

12 Key Points on WBS Identify all tasks to accomplish the project Use good judgement as the key to an effective WBS - no hard and fast rules Structure WBS as work will be done Levels of detail should allow for realistic estimating Levels of detail should allow assignment to single organizational control unit 12

13 Key Points on WBS (continued) Limit level of detail to level of control Each lowest level task should result in a deliverable Each WBS description should include an action verb, for example - Establish manufactuarability criteria Prepare final product proposal package Update common software Each task should have single, identifiable owner 13

14 Key Messages The WBS is the cornerstone off quality project planning The WBS is a tool, not an end unto itself There are multiple uses of the WBS The WBS is not a schedule The WBS is a good project team-building tool 14