Page 71 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Unit 3: Work Breakdown Structure

3.1 Uses for the WBS Notes

The WBS has four uses:
1. Thought process tool: The manager and the project team use WBS as a thought process tool
that helps them to visualize exactly how the work of the project can be defined and
managed effectively.
2. Architectural design tool: WBS can be used as a design tool as it is a picture of the work of
the project that shows how the items of work are related to one another.
3. Planning tool: In the planning phase, the WBS gives the project team a detailed
representation of the project as a collection of activities that must be completed in order
for the project to be completed. It is at the lowest activity level of WBS that we will
estimate effort, elapsed time, and resource requirements; build a schedule of when the
work will be completed; and estimate deliverable dates and project completion.
4. Project status reporting tool: The WBS is used as a structure for reporting project status.
The project activities are consolidated (that is, rolled up) from the bottom as lower-level
activities are completed. As work is completed, activities will be completed. Completion
of lower-level activities causes higher-level activities to be partially complete. Some of
these higher-level activities may represent significant progress whose completion will be
milestone events in the course of the project.

Task The WBS defines milestone events that can be reported to senior management and
to the customer. Analyze

WBS and the Project Manager

It is the project manager who decides on the architecture of the WBS and the level of detail
required. This detail is important because the project manager is accountable for the success of
the project. The WBS must be defined so that the project manager can manage the project. Apart
from any senior management requirements for reporting or organizational requirements for
documentation or process, the project manager is free to develop the WBS according to his or her
needs and those of management.

3.2 Generating the WBS

The best way to generate the WBS is as part of the Joint Project Planning (JPP) session. One of two
simple decomposition processes is used to identify the activities that must be performed from
the beginning to the completion of the project. These activities are the lowest level of managed
work for the project manager. At this point in the planning process, you should have completed
the Project Overview Statement. You may have to go back and reconsider the POS as a result of
further planning activities, but for now let’s assume the POS is complete. Our technique for
generating the WBS will reduce even the most complex project to a set of clearly defined activities.
The WBS will be the document that guides the remainder of the planning activities.
Two approaches can be used to identify the project activities:
 The first is the top-down approach.
 The second is the bottom-up approach.

LOVELY PROFESSIONAL UNIVERSITY 65