Skip to content

Operations Management and Strategic Management · Project Management, Monitoring and Control

Project Planning and Work Breakdown Structure Explained

Updated 10 October 2026 · Fact-checked

Project planning defines what must be done, in what order, by whom and by when. A work breakdown structure (WBS) splits the project into smaller deliverables and tasks. You then estimate durations, sequence the tasks, assign resources and show the schedule on a Gantt chart or milestone chart.

Understand Project Planning and Work Breakdown Structure

A project is a one-time effort with a clear objective, a start and an end date, a budget and limited resources. Building a warehouse, launching a new product or installing an ERP system are projects. Because they are not repeated, you cannot rely on routine. You need a plan.

Project planning answers four questions: what is to be done, how it will be done, who will do it, and when and at what cost. A typical sequence is:

  • Define the objective, scope and deliverables.
  • Break the work into smaller parts (the WBS).
  • Identify activities and their dependencies (which must finish before another starts).
  • Estimate time, cost and resources for each activity.
  • Build the schedule and the budget.
  • Set up monitoring and control, with reviews and milestones.

A work breakdown structure is a hierarchical, deliverable-oriented breakdown of the project. Level 1 is the whole project. Level 2 holds major deliverables or phases. Lower levels split these into work packages, the smallest units that can be assigned to one person or team, estimated and tracked. A good WBS covers 100% of the scope. Work not in the WBS is not in the project.

Scheduling turns the WBS into a timetable. You fix the sequence of activities, their durations, and the start and finish dates. Two simple tools show the schedule. A Gantt chart is a bar chart with activities listed down the side and time across the top. Each bar runs from the planned start to the planned finish. It is easy to read and shows progress, but it does not show dependencies well. A milestone chart marks only key events, such as approval received or machinery installed, with symbols against dates. It shows what has been reached, not how long each task takes.

For complex projects with many dependencies, network techniques such as CPM and PERT are used. The WBS feeds into them because it supplies the list of activities.

Key rules to remember

Hierarchy of a WBS
Project → Deliverables / Phases → Sub-deliverables → Work packages
Each lower level must add up to the level above it. No gaps and no overlaps.
Activity finish time
Finish date = Start date + Duration
Use the same time unit (days or weeks) throughout. Mind whether weekends count.
Start of a dependent activity
Earliest start = latest of the finish times of all its predecessors
An activity with two predecessors waits for the later one.
Project duration (simple sequence)
Total time = Σ durations of activities in sequence; for parallel paths, take the longest path
Activities done in parallel do not add up.
Gantt vs milestone chart
Gantt = activities against time (bars); Milestone = key events against dates (symbols)
Use this one-line contrast in comparison questions.

How to solve Project Planning and Work Breakdown Structure questions

Use this order for any question on planning, WBS or charts. It works for both theory and numerical questions.

  1. 1Read the question and note the project, its objective and any deadline or budget given.
  2. 2For a planning question, list the planning steps in order: objective and scope, WBS, activities and dependencies, time and resource estimates, schedule, budget, monitoring.
  3. 3For a WBS question, draw levels: project, major deliverables, sub-deliverables, work packages. Check that nothing is missing or duplicated.
  4. 4List each activity with its duration and predecessors in a small table.
  5. 5Compute the earliest start and finish of each activity: start = latest predecessor finish, finish = start + duration.
  6. 6Find total project time as the longest path. State it with the unit.
  7. 7Draw the chart asked for. For a Gantt chart, use bars on a time scale. For a milestone chart, mark key events on dates.
  8. 8Finish with one line of interpretation, such as which activities are critical or what delay would do.

Quickest way: Table, then chart

When to use it: Use this when a numerical question gives activities, durations and predecessors and asks for a schedule or Gantt chart, and you have under 10 minutes.

  1. Draw a table with columns: Activity, Duration, Predecessor, Start, Finish.
  2. Fill activities with no predecessor first. Start = 0.
  3. Move down the list. Start = highest finish among predecessors. Finish = start + duration.
  4. Project duration = highest finish value in the table.
  5. Draw the time axis once, with equal spacing. Draw each bar from Start to Finish.
  6. Mark milestones as small symbols at the finish of key activities.

Common mistakes in Project Planning and Work Breakdown Structure

  • Writing a WBS as a list of tasks in time order

    Students confuse a WBS with a schedule.

    Fix: Organise a WBS by deliverables and levels, not by sequence. Sequence belongs to scheduling.

  • Leaving out scope, such as testing or training, from the WBS

    Students list only the main production work.

    Fix: Check each branch against the project objective. Include management, testing, approvals and handover.

  • Adding durations of parallel activities

    Students total all durations without checking dependencies.

    Fix: Add only along a sequence. For parallel paths, take the longest one.

  • Saying a milestone chart shows activity durations

    Both charts are time-based, so students blur them.

    Fix: A milestone chart marks key events only. Bars with durations belong to the Gantt chart.

  • Claiming a Gantt chart clearly shows all dependencies

    Bars seem to imply order.

    Fix: Say it shows sequence and progress simply, but interdependencies are weak. Network diagrams handle them better.

  • Giving planning steps without any order or explanation

    Students memorise a list but not the logic.

    Fix: Number the steps and add a short phrase on what each produces, for example WBS gives the activity list.

Worked examples

Example 1

A company plans to set up a small packaging unit. Prepare a three-level work breakdown structure up to work packages for the project.

Show the solution
  1. Level 1 is the project: Setting up the packaging unit.
  2. Level 2 deliverables: A. Premises, B. Machinery, C. People and systems, D. Approvals and launch.
  3. Level 3 under A: A1 Lease and site selection, A2 Civil and electrical work.
  4. Under B: B1 Machine procurement, B2 Installation, B3 Trial run.
  5. Under C: C1 Recruitment, C2 Training, C3 Procedures and quality checks.
  6. Under D: D1 Licences and registrations, D2 Commercial start.
  7. Check: every item contributes to the objective, and nothing is repeated.

Answer: The WBS has the project at Level 1, four deliverables at Level 2 (premises, machinery, people and systems, approvals and launch), and about ten work packages at Level 3 that can each be assigned and tracked.

Example 2

A project has these activities: A (3 weeks, no predecessor), B (4 weeks, after A), C (2 weeks, after A), D (5 weeks, after B and C). Find the start and finish week of each activity and the project duration.

Show the solution
  1. A has no predecessor: start 0, finish 0 + 3 = 3.
  2. B follows A: start 3, finish 3 + 4 = 7.
  3. C follows A: start 3, finish 3 + 2 = 5.
  4. D follows B and C. Their finishes are 7 and 5. Start = the later one = 7.
  5. D finish = 7 + 5 = 12.
  6. Project duration = 12 weeks. The longest path is A, B, D (3 + 4 + 5 = 12). The path A, C, D gives 3 + 2 + 5 = 10.
  7. On the Gantt chart, B and C bars start together at week 3. C has 2 weeks of slack.

Answer: A: 0 to 3; B: 3 to 7; C: 3 to 5; D: 7 to 12. The project takes 12 weeks, and the sequence A, B, D decides it.

Exam tips

  • For compare questions, such as Gantt chart vs milestone chart, write points side by side: what it shows, detail level, dependencies, use, limitation.
  • In a WBS question, draw the hierarchy as an indented list. Label the levels and name the work packages.
  • In numerical questions, show the table of start and finish times. Step marks come from it even if the final figure is wrong.
  • Write the unit (days or weeks) with every answer.
  • In MCQs, watch for the word key events (milestone) versus activities with time bars (Gantt).

Practice questions from Project Management, Monitoring and Control

Project Planning and Work Breakdown Structure: frequently asked questions

What is a work breakdown structure in simple words?

It is a tree that splits a project into smaller and smaller parts until you reach work packages that one person or team can handle. It is built around deliverables. It helps in estimating cost and time and in assigning responsibility.

What is the difference between a Gantt chart and a milestone chart?

A Gantt chart shows each activity as a bar against time, so you see start, finish and progress. A milestone chart shows only key events and their dates. The Gantt chart gives more detail, while the milestone chart is better for senior management summaries.

What are the main steps in project planning?

Define the objective and scope, build the WBS, identify activities and dependencies, estimate time and resources, prepare the schedule and budget, and set up monitoring and control. State them in this order and add a short note on each.

Is the WBS the same as a project schedule?

No. The WBS lists what must be delivered and does not show timing. The schedule adds durations, sequence and dates to those items. The WBS comes first and supplies the activities for the schedule.