This page needs a newer browser to run its tools. You can still read everything here.

Scope and change control interview questions

Interview questions on scope and change control: short warm-ups, then what each harder question tests, the first step of a good answer and its follow-ups.

6 questions: 2 warm-ups and 4 with model answers · Levels: Fresher to staff

Warm-up questions

Short questions with short answers, each answered in full.

Fresher to mid

What is the 100 % rule of a work breakdown structure?

Answered in the lesson Scope statements and work breakdown structures
Fresher to mid

How do scope creep and gold plating differ?

Answered in the lesson Change control without bureaucracy

Questions with model answers

What each question tests, the first step of a good answer and the follow-ups to expect.

Mid to senior

A junior colleague's WBS for an office move has elements such as "pack boxes", "move desks" and "test network", and "IT equipment" appears under both "Furniture and equipment" and "IT". How do you coach them to fix it?
What it tests

Explaining deliverable-oriented decomposition, the 100 % rule and the line between the WBS and the schedule, and coaching rather than rewriting the work for them.

First step

Ask them what the move must deliver when it is finished, a working office, connected desks, an emptied old site, and rebuild the top levels from those answers together. Then add up the branches with them, so they see the IT equipment counted twice for themselves.
Follow-ups
- Where do "pack boxes" and "move desks" go instead?
- How far down should they decompose?
- How do you check the result without redoing it yourself?
From the lesson Scope statements and work breakdown structures
Model answer, Pro. Model answers open with any pass; prices are in the notice on this page.
Opening the model answers with your pass…
Model answers open with any MySmartCoPilot pass.
Pro pass · 1 week₹79$2.99
30 days₹179$5.99
1 year₹1,699$45
One payment; a pass never renews. The price shown is the total you pay: no fees or charges are added at checkout.
Passes can’t be bought right now, so the model answers can’t be opened at the moment. If you have a pass, enter your licence key.
Choose a pass I have a licence key
It also opens every other in-depth part in Learn and every Pro tool. Sales are final, except where the law gives you a right to withdraw, for example in the EU and the UK (refund policy).
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes
Senior to staff

A client wants a fixed price for a mobile app, but also wants to change its features every two weeks after seeing progress. How do you structure the scope, and what do you put in the contract?
What it tests

Combining a WBS for fixed commitments with a backlog for emerging features, and expressing that combination in a contract that protects both sides.

First step

Separate what can be fixed from what will be discovered. Payments, security, accessibility and the release itself can be fixed deliverables in a WBS with acceptance criteria; the features go into an ordered backlog within a fixed budget of capacity, which the client reorders every two weeks.
Follow-ups
- The client insists every feature is fixed now. What then?
- How is a swap of features priced?
- How do you report progress to the client?
From the lesson Scope statements and work breakdown structures
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes
Mid to senior

A senior sponsor keeps asking developers directly for "small" additions that never go through change control. You estimate that three weeks of work have gone that way and the next milestone is now at risk. What do you do?
What it tests

Confronting scope creep from a powerful stakeholder with evidence, restoring the change route without blocking the sponsor, and re-planning honestly.

First step

Gather the evidence first: list the additions, the hours each took and what they displaced. Then meet the sponsor privately, show the list and its effect on the milestone, and propose a fast route for their requests, such as a same-day impact note, rather than a ban.
Follow-ups
- The sponsor says the additions are too small to log. What do you answer?
- Should the three weeks of work be undone?
- What do you tell the developers?
From the lesson Change control without bureaucracy
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes
Senior to staff

On day 3 of a ten-day Sprint, a new regulation requires a consent screen within 30 days. The Product Owner wants to cancel the Sprint and start again. What do you advise?
What it tests

Applying the Scrum Guide's rules on change and cancellation, judging whether the Sprint Goal is really obsolete, and planning a regulatory deadline through the backlog.

First step

Ask whether the regulation makes the current Sprint Goal pointless. If the goal still has value, the work fits through the backlog: 30 days leaves room for the next Sprints, so the consent screen goes to the top of the Product Backlog, sized now, and is built in the next Sprint.
Follow-ups
- When would cancelling the Sprint be right?
- The screen needs 15 days of work. Does your answer change?
- Does the project's change control have a part here?
From the lesson Change control without bureaucracy
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes

All Project Management & Agile interview questions · The Project Management & Agile track

Warm-up questions

What is the 100 % rule of a work breakdown structure?

How do scope creep and gold plating differ?

Questions with model answers

A junior colleague's WBS for an office move has elements such as "pack boxes", "move desks" and "test network", and "IT equipment" appears under both "Furniture and equipment" and "IT". How do you coach them to fix it?

A client wants a fixed price for a mobile app, but also wants to change its features every two weeks after seeing progress. How do you structure the scope, and what do you put in the contract?

A senior sponsor keeps asking developers directly for "small" additions that never go through change control. You estimate that three weeks of work have gone that way and the next milestone is now at risk. What do you do?

On day 3 of a ten-day Sprint, a new regulation requires a consent screen within 30 days. The Product Owner wants to cancel the Sprint and start again. What do you advise?