PRACTICAL: WORK BREAKDOWN STRUCTURE (WBS) IN PROJECT MANAGEMENT
1. Aim of the Practical
To understand, design, and implement a Work Breakdown Structure (WBS) for a software project in order to divide the project into manageable tasks and improve planning, execution, and control.
2. Objectives
After completing this practical, students will be able to:
Understand the concept of Work Breakdown Structure
Break a project into smaller, manageable components
Organize tasks hierarchically
Identify deliverables and sub-deliverables
Improve project planning and resource allocation
Apply WBS to real-world software development projects
3. Introduction
In project management, handling a complete project as a single unit is difficult. Therefore, the project is divided into smaller parts. This division is called a Work Breakdown Structure (WBS).
A WBS is a hierarchical decomposition of a project into smaller components. It organizes work into manageable sections, making it easier to plan, execute, monitor, and control.
In Computer Science projects, WBS is especially useful because software projects involve multiple stages such as requirement analysis, design, coding, testing, and deployment.
4. Definition of WBS
A Work Breakdown Structure (WBS) is a structured decomposition of a project into smaller, manageable parts called work packages, which can be easily planned, scheduled, and controlled.
5. Importance of WBS
5.1 Better Planning
Breaking the project into smaller tasks helps in detailed planning.
5.2 Improved Time Management
Each task can be assigned a timeline.
5.3 Resource Allocation
Resources can be assigned efficiently.
5.4 Risk Reduction
Identifying smaller tasks helps in detecting risks early.
5.5 Easy Monitoring
Progress can be tracked at each level.
6. Key Concepts of WBS
6.1 Deliverables
The outputs or results of each phase.
6.2 Work Packages
The smallest unit of work in WBS.
6.3 Levels in WBS
Level 1: Project
Level 2: Major Deliverables
Level 3: Subtasks
Level 4: Work Packages
6.4 100% Rule
The WBS must include 100% of the work required to complete the project.
7. Types of WBS
7.1 Deliverable-Based WBS
Organized around outputs.
7.2 Phase-Based WBS
Organized according to project phases.
8. Steps to Create a WBS
Step 1: Define the Project Scope
Clearly understand what the project aims to achieve.
Step 2: Identify Major Deliverables
Divide the project into main sections.
Step 3: Break Down Deliverables
Divide each deliverable into smaller tasks.
Step 4: Define Work Packages
Continue breaking down until tasks are manageable.
Step 5: Review the WBS
Ensure completeness and correctness.
9. Example Project for WBS
Project Title:
Library Management System
10. WBS Structure Example
Level 1: Project
Library Management System
Level 2: Major Deliverables
Requirement Analysis
System Design
Development
Testing
Deployment
Level 3 & 4: Detailed Breakdown
1. Requirement Analysis
Collect Requirements
Analyze Requirements
Prepare SRS
2. System Design
Database Design
UI Design
Architecture Design
3. Development
Frontend Development
Backend Development
Database Implementation
4. Testing
Unit Testing
Integration Testing
System Testing
5. Deployment
Installation
User Training
Maintenance
11. Graphical Representation of WBS
WBS can be represented as:
Tree Diagram
Outline Format
Tabular Format
Example (Tree Structure)
Project: Library Management System
|
|-- Requirement Analysis
| |-- Requirement Gathering
| |-- Documentation
|
|-- Design
| |-- UI Design
| |-- Database Design
|
|-- Development
| |-- Coding
| |-- Integration
|
|-- Testing
| |-- Unit Testing
| |-- System Testing
|
|-- Deployment
|-- Installation
|-- Maintenance
12. Tools Used for WBS
Students can use:
MS Word (for documentation)
MS Excel (for tabular WBS)
Project Management Software
Drawing tools (Lucidchart, Draw.io)
13. Advantages of WBS
Simplifies complex projects
Improves communication
Enhances productivity
Helps in cost estimation
Supports scheduling
14. Disadvantages of WBS
Time-consuming
Requires expertise
May become complex for large projects
15. Role of WBS in Software Development
In Computer Science projects, WBS helps in:
Dividing coding tasks
Managing modules
Assigning responsibilities
Tracking development progress
16. Practical Implementation
Task:
Create a WBS for a Student Management System
Steps:
Identify project scope
List major modules
Break into sub-modules
Create hierarchical structure
Sample WBS:
Project: Student Management System
1. Planning
Requirement Gathering
Feasibility Study
2. Design
UI Design
Database Design
3. Development
Student Module
Teacher Module
Admin Module
4. Testing
Unit Testing
Integration Testing
5. Deployment
Installation
Maintenance
17. WBS vs Other Tools
Feature
WBS
Gantt Chart
Purpose
Task Breakdown
Scheduling
Structure
Hierarchical
Timeline
Focus
Work Division
Time
18. Common Mistakes in WBS
Ignoring small tasks
Overlapping tasks
Too much detail or too little detail
Not following 100% rule
19. Best Practices
Keep it simple
Use clear naming
Follow hierarchy
Validate with team
Update regularly
20. Viva Questions
What is WBS?
Why is WBS important?
What is a work package?
What is the 100% rule?
Types of WBS?
Difference between WBS and Gantt chart?
What are levels in WBS?
What tools are used?
Advantages of WBS?
Role of WBS in software development?
21. Conclusion
Work Breakdown Structure (WBS) is a powerful tool in project management that helps in dividing complex projects into manageable tasks. For polytechnic students, learning WBS improves their ability to plan, organize, and execute projects efficiently. It acts as a foundation for scheduling, cost estimation, and risk management.
22. Result
The Work Breakdown Structure for the selected project was successfully created and analyzed, demonstrating effective project planning and task management.
23. Precautions
Ensure all tasks are included
Avoid duplication
Maintain clarity
Keep structure simple
