Work Breakdown Structure (WBS) in Software Engineering - Mini Project: Build & Apply

Creating a Work Breakdown Structure (WBS)

📖 Scenario: You are managing a small software project to build a simple mobile app. To organize the work clearly, you want to create a Work Breakdown Structure (WBS) that lists all the main tasks and subtasks.

🎯 Goal: Build a clear Work Breakdown Structure (WBS) as a nested dictionary showing main tasks and their subtasks.

📋 What You'll Learn

Create a dictionary named wbs with main tasks as keys and lists of subtasks as values

Add a variable project_name to store the project title

Use a for loop to print each main task and its subtasks

Add a final summary string summary describing the total number of main tasks

💡 Why This Matters

🌍 Real World

Project managers use WBS to organize and plan all the work needed for a project clearly and simply.

💼 Career

Understanding WBS helps in roles like project management, software development planning, and team coordination.

1

Set up the initial Work Breakdown Structure dictionary

Create a dictionary called wbs with these exact entries: 'Design': ['UI Design', 'UX Research'], 'Development': ['Frontend', 'Backend'], and 'Testing': ['Unit Testing', 'Integration Testing'].

Software Engineering

# Create the wbs dictionary with main tasks and subtasks
# Your code here

Hint

Use a dictionary with keys as main tasks and values as lists of subtasks.

2

Add the project name variable

Create a variable called project_name and set it to the string 'Mobile App Project'.

Software Engineering

wbs = {
    'Design': ['UI Design', 'UX Research'],
    'Development': ['Frontend', 'Backend'],
    'Testing': ['Unit Testing', 'Integration Testing']
}
# Create the project_name variable
# Your code here

Hint

Assign the exact string to the variable project_name.

3

Loop through the WBS to list tasks and subtasks

Use a for loop with variables main_task and subtasks to iterate over wbs.items(). Inside the loop, create a string task_list that joins the subtasks with commas.

Software Engineering

wbs = {
    'Design': ['UI Design', 'UX Research'],
    'Development': ['Frontend', 'Backend'],
    'Testing': ['Unit Testing', 'Integration Testing']
}

project_name = 'Mobile App Project'

for main_task, subtasks in wbs.items():
    # Create task_list string joining subtasks
    # Your code here

Hint

Use for main_task, subtasks in wbs.items(): and task_list = ', '.join(subtasks).

4

Add a summary string with the total number of main tasks

Create a string variable called summary that uses an f-string to say: 'The project has X main tasks.' where X is the number of keys in wbs.

Software Engineering

wbs = {
    'Design': ['UI Design', 'UX Research'],
    'Development': ['Frontend', 'Backend'],
    'Testing': ['Unit Testing', 'Integration Testing']
}

project_name = 'Mobile App Project'

for main_task, subtasks in wbs.items():
    task_list = ', '.join(subtasks)

summary = ''  # Create summary string here
# Your code here

Hint

Use an f-string with len(wbs) to count main tasks.

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