ScholarQuill logoScholarQuillUniversity Notes
  • Notes
  • Past Papers
  • Blogs
  • Todo
Login
ScholarQuill logoScholarQuillUniversity Notes
Login
NotesPast PapersBlogsTodo
More
SubjectsDiscussionCGPA CalculatorGPA CalculatorStudent PortalCourse Outline
About
About usPrivacy PolicyReportContact
Notes
Past Papers
Blogs
Todo
Analytics
    Current Subject
    🧩
    Software Project Management
    ITEC3131
    Progress0 / 42 topics
    Topics
    1. Introduction Software Project: Classification of project types2. Scope triangle3. Project risk vs business value4. The S curve5. Five phases of project management life cycle6. WBS: Work Breakdown Structure7. Estimate activity duration8. Five methods of Estimating Activity Duration9. Elapsed Time vs Productive time10. PMI Process Groups & Knowledge Areas11. Project Planning and Project Scheduling12. Project Proposal13. Project Networks: Critical Path Method (CPM)14. Build the project network15. Analysis of the project network16. Network Analysis and Critical Path Analysis17. PERT18. GANTT Chart19. Using MS-Project to draw GANTT chart20. Project Metrics & Software Project Estimation21. Software Project Metrics: Metrics & Indicators22. Software measurement: Size Oriented Metrics23. Function-Oriented Metrics24. Software Project Estimation: Decomposition Techniques25. Software Sizing26. Problem-Based Estimation27. Cost Estimation28. Size Estimation: COCOMO Model29. Function Point Analysis30. Project Staffing31. Project Monitoring and Control32. Project Staffing and Personnel Planning33. Software project Teams34. Risk Identification, Analysis and Management35. Earned Value Analysis36. Configuration Management37. Earned Value Analysis for Project Monitoring and Control38. Software Project Quality Assurance Plans39. SQA Process40. Software Project Quality Standards41. Overview of Project Configuration Management42. Project Risk Management
    ITEC3131›WBS: Work Breakdown Structure
    Software Project ManagementTopic 6 of 42

    WBS: Work Breakdown Structure

    3 minread
    498words
    Beginnerlevel

    📘 Work Breakdown Structure (WBS)


    🔹 1. Definition

    A Work Breakdown Structure (WBS) is a hierarchical decomposition of a project into smaller, manageable components called work packages.

    👉 In simple words: It breaks a big project into small pieces so it becomes easier to plan, manage, and control.


    🔹 2. Purpose of WBS

    • Makes complex projects easier to understand
    • Helps in planning, scheduling, and costing
    • Assigns clear responsibilities
    • Improves time and resource estimation
    • Ensures no work is missed

    🔹 3. Key Concepts

    🔸 1. Hierarchical Structure

    • Top → Entire project
    • Middle → Major deliverables
    • Bottom → Small tasks (work packages)

    🔸 2. Work Package

    • The smallest unit of work in WBS
    • Can be assigned, scheduled, and cost estimated

    👉 Example: “Design login page UI”


    🔸 3. 100% Rule ⭐ (Very Important)

    The WBS must include 100% of the total project work (no more, no less).

    👉 Meaning:

    • Include all tasks
    • Avoid duplication

    🔸 4. Deliverable-Oriented

    • Focuses on outputs (results), not just activities

    🔹 4. Levels of WBS

    Level 1: Project

    ➡ Entire project (e.g., “E-commerce Website”)

    Level 2: Major Components

    ➡ Modules (e.g., UI, Backend, Database)

    Level 3: Subtasks

    ➡ Smaller tasks (e.g., Login system)

    Level 4: Work Packages

    ➡ Detailed actionable tasks


    🔹 5. Types of WBS

    🔸 1. Deliverable-Based WBS

    • Organized by project outputs

    👉 Example:

    • Website → UI → Login Page

    🔸 2. Phase-Based WBS

    • Organized by project phases

    👉 Example:

    • Planning → Design → Development → Testing

    🔹 6. Example of WBS

    📌 Project: Online Shopping System

    1. Online Shopping System
       1.1 Requirements
       1.2 Design
           1.2.1 UI Design
           1.2.2 Database Design
       1.3 Development
           1.3.1 Frontend
           1.3.2 Backend
       1.4 Testing
       1.5 Deployment
    

    🔹 7. Diagram Description

    📌 WBS looks like a tree structure:

    • Top node → Project
    • Branches → Major tasks
    • Leaves → Work packages

    👉 Similar to an organizational chart


    🔹 8. Advantages of WBS

    • Better project organization
    • Easier task assignment
    • Improved cost and time estimation
    • Helps in risk identification
    • Enhances team coordination

    🔹 9. Common Mistakes

    ❌ Missing tasks (violating 100% rule) ❌ Too much detail (over-complication) ❌ Not focusing on deliverables ❌ Overlapping tasks


    🔹 10. Important Exam Points

    • WBS = Hierarchical breakdown
    • Smallest unit = Work Package
    • Follow 100% Rule
    • Can be deliverable-based or phase-based
    • Used in planning and scheduling

    🔹 11. Short Summary

    • WBS divides a project into manageable parts
    • Helps in planning, estimation, and control
    • Ensures complete coverage of project work
    • Key concept: 100% Rule + Work Packages

    🔹 12. Quick Exam Answer (2–3 lines)

    A Work Breakdown Structure (WBS) is a hierarchical decomposition of a project into smaller components called work packages. It helps in planning, organizing, and managing the project effectively while ensuring all work is included.


    🔹 13. Likely Exam Questions

    1. Define Work Breakdown Structure (WBS).
    2. Explain the 100% rule in WBS.
    3. What is a work package?
    4. Draw and explain a WBS diagram.
    5. Differentiate between deliverable-based and phase-based WBS.
    6. What are the advantages of using WBS?
    7. Explain the levels of WBS with examples.
    Previous topic 5
    Five phases of project management life cycle
    Next topic 7
    Estimate activity duration

    Past Papers

    Open this section to load past papers

    Click on Show Past Papers to see past papers.
    On This Page
      Reading Stats
      Est. reading time3 min
      Word count498
      Code examples0
      DifficultyBeginner