Work Breakdown Structure (WBS) in Software Engineering - Step-by-Step Execution

Concept Flow - Work Breakdown Structure (WBS)

Start Project

↓

Define Major Deliverables

↓

Break Deliverables into Sub-deliverables

↓

Break Sub-deliverables into Work Packages

↓

Assign Work Packages to Teams

↓

Manage and Track Progress

↓

Project Complete

The WBS process starts by defining major deliverables, then breaking them down into smaller parts until manageable work packages are created, which are assigned and tracked.

Execution Sample

Software Engineering

Project
  |- Design
      |- UI Design
      |- Backend Design
  |- Development
      |- Frontend
      |- Backend
  |- Testing
      |- Unit Tests
      |- Integration Tests

This shows a simple WBS tree breaking a project into design, development, and testing, then further into smaller tasks.

Analysis Table

Step	Action	Result	Next Step
1	Identify major deliverables	Design, Development, Testing	Break down Design
2	Break down Design	UI Design, Backend Design	Break down Development
3	Break down Development	Frontend, Backend	Break down Testing
4	Break down Testing	Unit Tests, Integration Tests	Assign work packages
5	Assign work packages	Teams assigned to each package	Track progress
6	Track progress	Monitor completion of packages	Project complete
7	Project complete	All work packages done	End

💡 All work packages are assigned and tracked until project completion.

State Tracker

WBS Level	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Major Deliverables	None	Design, Development, Testing	Design, Development, Testing	Design, Development, Testing	Design, Development, Testing	Design, Development, Testing
Sub-deliverables	None	None	UI Design, Backend Design	UI Design, Backend Design, Frontend, Backend	UI Design, Backend Design, Frontend, Backend, Unit Tests, Integration Tests	All sub-deliverables listed
Work Packages	None	None	None	None	All work packages defined	All packages assigned and tracked

Key Insights - 3 Insights

Why do we break deliverables into smaller parts instead of working on the big deliverable directly?

Breaking deliverables into smaller parts makes work manageable and easier to assign and track, as shown in execution_table steps 2-4.

Is the WBS a list of tasks or a hierarchy of deliverables?

WBS is a hierarchy of deliverables broken down into smaller deliverables and work packages, not just a flat task list, as seen in the execution_sample structure.

When do we assign teams to work packages in the WBS process?

Teams are assigned after breaking down all deliverables into work packages, as shown in execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what are the major deliverables identified at Step 1?

A UI Design, Backend Design

B Design, Development, Testing

C Frontend, Backend

D Unit Tests, Integration Tests

💡 Hint

Check the 'Result' column at Step 1 in the execution_table.

At which step are teams assigned to work packages according to the execution_table?

A Step 3

B Step 2

C Step 5

D Step 6

💡 Hint

Look for the action 'Assign work packages' in the execution_table.

According to variable_tracker, what happens to sub-deliverables after Step 4?

A They include UI Design, Backend Design, Frontend, Backend, Unit Tests, Integration Tests

B They remain undefined

C Only major deliverables are listed

D Work packages are assigned

💡 Hint

Check the 'Sub-deliverables' row after Step 4 in variable_tracker.

Concept Snapshot

Work Breakdown Structure (WBS):
- Break project into major deliverables
- Each deliverable breaks into smaller sub-deliverables
- Continue until manageable work packages
- Assign work packages to teams
- Track progress until project completion

Full Transcript

Work Breakdown Structure (WBS) is a method to organize a project by breaking it down into smaller parts. First, major deliverables are identified. Then each deliverable is divided into smaller sub-deliverables. This continues until the work is broken into manageable work packages. These packages are assigned to teams for execution. Progress is tracked until all work packages are completed and the project finishes. This step-by-step breakdown helps manage complex projects by making tasks clear and assignable.

Practice

1. What is the main purpose of a Work Breakdown Structure (WBS) in project management?

easy

A. To divide a large project into smaller, manageable tasks

B. To assign salaries to team members

C. To create a marketing plan

D. To write the final project report

Solution

1. Step 1: Understand the definition of WBS

   A Work Breakdown Structure is used to break down a big project into smaller parts that are easier to manage.

2. Step 2: Match the purpose with the options

   Only To divide a large project into smaller, manageable tasks describes breaking a project into smaller tasks, which is the main purpose of WBS.

3. Final Answer:

   To divide a large project into smaller, manageable tasks -> Option A

4. Quick Check:

   WBS = Divide project into smaller tasks [OK]

Hint: WBS breaks big projects into small tasks [OK]

Common Mistakes:

• Confusing WBS with budgeting or reporting
• Thinking WBS is for marketing plans
• Assuming WBS assigns salaries

2. Which of the following is the correct way to represent a Work Breakdown Structure (WBS)?

easy

A. A flat list of unrelated tasks

B. A tree or outline showing tasks and sub-tasks

C. A pie chart of project costs

D. A random collection of project documents

Solution

1. Step 1: Recall the format of WBS

   A WBS is usually shown as a tree or outline that organizes tasks and sub-tasks hierarchically.

2. Step 2: Compare options with WBS format

   Only A tree or outline showing tasks and sub-tasks describes a tree or outline format, which matches the WBS structure.

3. Final Answer:

   A tree or outline showing tasks and sub-tasks -> Option B

4. Quick Check:

   WBS format = tree or outline [OK]

Hint: WBS looks like a tree or outline [OK]

Common Mistakes:

• Choosing flat lists without hierarchy
• Confusing WBS with charts or documents
• Ignoring task-subtask relationships

3. Consider this partial WBS outline:

1. Build Website
  1.1 Design
  1.2 Development
    1.2.1 Frontend
    1.2.2 Backend
  1.3 Testing

Which task is a sub-task of Development?

medium

A. Testing

B. Design

C. Frontend

D. Build Website

Solution

1. Step 1: Identify the Development task and its sub-tasks

   Development is task 1.2, and its sub-tasks are 1.2.1 Frontend and 1.2.2 Backend.

2. Step 2: Match the options with sub-tasks of Development

   Only Frontend (1.2.1) is a sub-task of Development; Design and Testing are separate tasks.

3. Final Answer:

   Frontend -> Option C

4. Quick Check:

   Sub-task of Development = Frontend [OK]

Hint: Look for numbering under Development (1.2.x) [OK]

Common Mistakes:

• Choosing sibling tasks instead of sub-tasks
• Confusing main tasks with sub-tasks
• Ignoring numbering hierarchy

4. A project manager created this WBS:

1. Project Start
2. Planning
3. Execution
4. Closing
5. Budgeting

What is wrong with this WBS?

medium

A. The numbering should start from zero

B. The tasks are not in alphabetical order

C. It includes budgeting which is not part of projects

D. It lacks sub-tasks breaking down each main task

Solution

1. Step 1: Check the structure of the WBS

   The WBS shows only main tasks without any sub-tasks or breakdowns.

2. Step 2: Identify the issue with missing details

   A proper WBS breaks tasks into smaller parts; this one misses that, making it incomplete.

3. Final Answer:

   It lacks sub-tasks breaking down each main task -> Option D

4. Quick Check:

   WBS needs sub-tasks = missing here [OK]

Hint: WBS must show smaller parts under main tasks [OK]

Common Mistakes:

• Thinking alphabetical order matters
• Believing budgeting is never part of projects
• Assuming numbering starts at zero

5. You have a project to organize a conference. Which of these is the best way to start creating a WBS?

hard

A. List all major deliverables like Venue, Speakers, and Marketing, then break each into smaller tasks

B. Write a detailed budget before listing any tasks

C. Start by assigning tasks to team members immediately

D. Create a random list of activities without grouping

Solution

1. Step 1: Understand the WBS creation process

   Start by identifying major deliverables or parts of the project, then break them into smaller tasks.

2. Step 2: Evaluate the options for starting a WBS

   List all major deliverables like Venue, Speakers, and Marketing, then break each into smaller tasks correctly describes starting with major deliverables and breaking them down, which is the best practice.

3. Final Answer:

   List all major deliverables like Venue, Speakers, and Marketing, then break each into smaller tasks -> Option A

4. Quick Check:

   Start WBS with major deliverables [OK]

Hint: Begin WBS with big parts, then split smaller [OK]

Common Mistakes:

• Starting with budget instead of tasks
• Assigning tasks before planning
• Making unorganized random lists