Project Mngmnt - week 4 - WBS


Terms in this set (...)

Project planning tool - aggregation of all work to be performed in a project
T/F: WBS is created once objectives are defined
WBS subdivides project into a hierarchy of tasks that are ...
What does WBS ensure?
that project activities are identified during planning phase so planning can be properly done
WBS Purpose (4)
1. defines activities of project
2. foundation of detail: planning, budget, scheduling, and controlling
3. provides global n overall detailed view of project
4. basis to generate network diagram
Activity Characteristics
1. status/completion must be memorable
2. definite start and finish
3. the time/cost must be easily estimated
4. assignment of activity must be manageable, measureable, and independent
Approaches to develop WBS (6)
1. Product Component Approach
2. Functional Approach
3. Geographical Area Approach
4. Organizational Approach
5. Top Down
6. Bottom Up
Product Component Approach
structuring work based on work products ex. design documents, manuals, delivered system
Functional Approach
Structuring work based on development activities and project functions ex. analysis, design, implementation, integration
Geographical Area Approach
structuring work based on geographical location ex. Munich team, Pittsburgh team, off-shore team
Organizational Approach
structuring work based on organizational structure ex. R&D dep., predevelopment, product development, marketing, sales
How to develop a good WBS (2)
1. Top Down Approach
2. Bottom Up Approach
Top Down Approach
start at highest, top level activities and develop increasing levels of details for all activities
Bottom Up Approach
generate all activities you can think of that will have to be done and then group them into categories
Whichever approach you choose for developing a WBS is dependent on ...
- familiarity with the project
- if similar projects have been performed before
- the amount of methods and technologies that will be used
Steps for Top Down Development
1. specify activities & sub-activities required
2. continue until project is broken down into doable tasks
Steps for Bottom Up Development
1. Brainstorm - write everything down and don't worry about overlap
2. analyze and group activities into major categories
3. organize higher level and lower level
4. use top-down approach to determine any other activities overlooked
The criteria used to determine the amount of detail in a WBS depends on:
1. degree at which people can be assigned responsibility and accountability for the tasks
2. degree at which you want to control and collect cost data during project
T/F: there is no single correct WBS for any project
True: two different groups can come up with different WBS's for the same project
Methods to identify what activities need to be done (4)
1. talk to experts
2. brainstorm with team
3. Interview stakeholders
4. Research past projects that are similar