A Work Breakdown Structure includes dividing a large and complex project into simpler, manageable and independent tasks. The root of this tree (structure) is labelled by the Project name itself. For constructing a work breakdown structure, each node is recursively decomposed into smaller sub-activities, until at the leaf level, the activities becomes undividable and independent. It follows a Top-Down approach.
- Step-1: Identify the major activities of the project.
- Step-2: Identify the sub-activities of the major activities.
- Step-3: Repeat till undividable, simple and independent activities are created.
Construction of Work Breakdown Structure:
Firstly, the project managers and top level management identifies the main deliverables of the project. After this important step, these main deliverables are broke down into smaller higher-level tasks and this complete process is done recursively to produce much smaller independent tasks. It depends on the project manager and team that upto which level of detail they want to break down their project.
Generally the lowest level tasks are the most simplest and independent tasks and takes less than two weeks worth of work. Hence, there is no rule for upto which level we may build the work breakdown structure of the project as it totally depends upon the type of project we are working on and the management of the company. The efficiency and success of the whole project majorly depends on the quality of the Work Breakdown Structure of the project and hence, it implies its importance.
- It allows to do a precise cost estimation of each activity.
- It allows to estimate the time that each activity will take more precisely.
- It allows easy management of the project.
- It helps in proper organisation of the project by the top management.
- Software Engineering | Project size estimation techniques
- Software Engineering | Architectural Design
- Software Engineering | Halstead’s Software Metrics
- Software Engineering | COCOMO Model
- Software Engineering | Classification of Software Requirements
- Software Engineering | Classical Waterfall Model
- Software Engineering | Iterative Waterfall Model
- Software Engineering | Spiral Model
- Software Engineering | Requirements Engineering Process
- Software Engineering | Requirements Elicitation
- Software Engineering | System configuration management
- Software Engineering | Challenges in eliciting requirements
- Software Engineering | Classification of Software
- Software Engineering | Rapid application development model (RAD)
- Software Engineering | Black box testing
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.