How do you create a work breakdown structure for a new project?
What the interviewer wants to hear
- Start from the scope statement and deliverables
- Decompose deliverables into smaller pieces down to work packages
- Follow the 100% rule
- Involve the team who will do the work
- Write a WBS dictionary and use it for estimates, schedule and ownership
Model answer
I start from the approved scope statement and list the main deliverables, for example design, software, training and data migration. Then, with the people who will do the work, I break each deliverable down into smaller parts until I reach work packages that can be estimated, assigned to one owner and tracked, often around one to two weeks of effort. I follow the 100% rule, meaning the WBS includes all the work in scope and nothing outside it, and each level fully adds up to the level above. I focus on deliverables, not activities, at the upper levels. For each work package I write a short WBS dictionary entry with a description, acceptance criteria and owner. The WBS then becomes the base for estimating, building the schedule, assigning responsibilities and spotting scope creep, because anything not in it needs a change request.
Can you answer it under time pressure?
Take a timed easy round and get scored on every answer.
More easy Project Manager questions
- Describe the main phases of a project lifecycle.
- How do you manage risks on a project?
- How do you keep stakeholders informed during a project?
- What is the difference between agile and waterfall, and when would you use each?
- How do you track whether a project is on track?
- What is the difference between a project, a program and a portfolio?
- What goes into a good project management plan?
- How is a Scrum Master different from a project manager?
- How do you make project meetings effective?