All jobs / Project / delivery manager
Project Management Fundamentals interview questions
Project Management Fundamentals questions a Project / delivery manager can be asked, from first job to senior. Open one to see the strongest answer and why it works.
A sponsor fixes the scope, the date and the budget on day one. What do you say?
The strongest answer: Something has to flex — if all three are fixed, quality or team health gives silently, so I ask which one the sponsor would move first and write that down
Why it works: Exactly — scope, time and cost are linked; naming the one that flexes up front is what keeps the plan honest.
- One constraint must flex.
- Name scope, time and cost together.
- Ask which one moves first.
- Write the agreed flex down.
Why write down what is out of scope, not only what is in?
The strongest answer: Because most disputes come from things each side assumed — an explicit out-of-scope list surfaces those assumptions now, while they are cheap to argue about
Why it works: Right — the out-of-scope list is where the unspoken expectations live; finding them early is the point.
- Exclusions catch assumptions.
- List what is not included.
- Review it with the stakeholder.
- Route changes through a conversation.
A senior developer is allocated half-time to your project and half-time to another. Both project plans assume her full-time.
What do you do?
The strongest answer: I surface the double-booking to both project owners and their manager this week, replan with her real capacity, and agree who gets priority when the two collide
Why it works: Exactly — the conflict is between the two plans, not inside the person; fix it where it lives, with the people who can decide.
- Over-allocation is a plan defect.
- Surface it to both owners.
- Plan with real capacity.
- Agree the priority rule.
Mid-sprint a stakeholder adds a “tiny” extra that is not the goal. Strongest move?
The strongest answer: I put it next to the goal and I ask what we drop or whether it waits — I do not swallow it because it is small
Why it works: Exactly. Small is still scope. Trade or wait. Do not hide it.
- Show it against the goal.
- Drop something or wait.
- Do not hide it in a ticket.
- Offer a later range if it waits.
The team hits dates by staying late in the last week of every sprint. What do you change?
The strongest answer: The system: WIP, slice size, and when we say a range — I do not thank the late nights as the plan
Why it works: Exactly. Recurring heroics are a design smell. Change WIP and honesty, not snacks.
- Treat late nights as a smell.
- Change WIP and slice size.
- Say the range earlier.
- Do not fund heroics with pizza.
A project is running late. The sponsor offers two contractors from next Monday to catch up.
How do you respond?
The strongest answer: I ask what they would work on: only well-separated, well-specified work helps — onboarding and coordination cost the existing team time first, so I would rather cut scope or restate the range
Why it works: Right — new people cost the team before they pay back; whether they help depends on the shape of the work, and scope or date are the honest levers.
- People cost before they help.
- Ask what they would work on.
- Prefer scope or range moves.
- Never keep a date you doubt.
A sponsor says: “ship it now, we will fix the quality after launch.” The team says the release is not stable.
How do you frame the decision?
The strongest answer: I make the trade explicit: which quality attributes we cut, what that costs after launch in incidents, support and rework, who carries the risk — and the sponsor’s decision goes on record
Why it works: Exactly — quality is the constraint that gives silently; a senior makes it visible, priced and owned rather than deciding it alone.
- Price the quality trade.
- Name the attributes being cut.
- Name the post-launch cost.
- Get the risk owner on record.