Quick game
Your call
Everyday project management calls, from easy to hard. Pick what you’d do, then see the best answer and why.
Scope change · Easy
Round 1 · 1 / 6
Two weeks before launch, the CEO asks you to add a feature a big prospect wants in this release. What do you do first?
Why: Change control means the impact is assessed and the person who owns the decision makes it. Adding it because the team says it fits, or parking it for the next release, both make the CEO’s call for them.
Agile · Easy
Round 1 · 2 / 6
Mid-sprint, a sales VP messages a developer directly and asks them to drop everything for an urgent customer request. What should happen?
Why: The product owner owns priorities, so they decide, not the requester and not the team. Sprint scope isn’t untouchable either: the product owner can change it if the request is worth more than the sprint goal.
Risk · Medium
Round 1 · 3 / 6
Your launch depends on new GPU servers, and the supplier warns that lead times just stretched to five months. Nothing has slipped yet. What do you do?
Why: It’s a risk, not yet an issue, and it needs a response while there’s time, not just a log entry. Ordering is a good move, but changing the baseline goes through change control.
Stakeholders · Medium
Round 1 · 4 / 6
You’re rolling out a new internal AI tool. One department head keeps skipping the check-ins, and their team isn’t using the tool. What’s your first move?
Why: Start by listening. Resistance usually has a reason, like workload, a bad past rollout or a real gap in the tool. A one-on-one spent selling the benefits is still a pitch, and training their team works around the person who decides.
Conflict · Hard
Round 1 · 5 / 6
Two senior engineers disagree on the architecture for a key service, and the team has been stalled for a week. What’s the best way to resolve it?
Why: Collaborating on the problem is the preferred way to resolve conflict: judge against agreed criteria and get real commitment. Choosing yourself forces the outcome, splitting the designs is a compromise nobody owns, and a vote skips the merits.
Security risk · Hard
Round 1 · 6 / 6
Two days before release, a critical vulnerability is found in an open-source library you use. A proper patch takes a week, and the product lead wants to ship and patch later. What do you do?
Why: A risk this size is above the PM’s or the product lead’s authority to accept. Turning off the feature may well be the right fix, but the sponsor makes that call with the facts in front of them. Delaying on reflex makes the decision for them too.
Communication · Easy
Round 2 · 1 / 6
Your team is split between Tel Aviv and a US office, and status updates keep getting missed on one side or the other. What do you do?
Why: The gap is the plan, not the tool. Decide who needs what information, when and how, then pick the channel. A new channel, a longer email or another meeting only treat the symptom.
Team health · Easy
Round 2 · 2 / 6
Velocity has dropped for three sprints in a row, and in stand-ups the team says they’re stretched thin. What do you do?
Why: Find out what’s slowing the team before acting. A smaller commitment hides the cause, one-on-ones aimed at finding someone to blame break trust, and a new hire slows the team down at first.
Requirements · Medium
Round 2 · 3 / 6
Mid-sprint, the team realizes a story’s acceptance criteria can be read two ways, and each reading is a very different amount of work. What happens next?
Why: The product owner decides what “done” means, and asking now costs minutes. Building first and confirming later risks wasted work, and the retrospective is too late for this story.
Budget · Medium
Round 2 · 4 / 6
Six months into a 12-month program, you’ve spent 60% of the budget and finished about 45% of the work. What do you do?
Why: You’re getting about 75 cents of work for every dollar spent. Find out why, forecast where it lands, then let the sponsor choose. Asking for money or cutting scope before the analysis acts on a guess, and assuming front-loading is also a guess.
Vendors · Hard
Round 2 · 5 / 6
A vendor delivers a module that meets the contract’s written spec but not what your users actually need. The vendor wants sign-off and final payment. What do you do?
Why: Deliverables are accepted against the contract. It meets the spec, so you sign off, and holding payment would breach the contract. The real gap was in the requirements, so it’s a change request plus a lesson learned, not a side deal.
Resources · Hard
Round 2 · 6 / 6
In a matrix org, a functional manager moves your only data engineer to a VP’s project for two weeks, and your critical path runs through their work. What do you do first?
Why: In a matrix, the functional manager owns the person’s time, so start with them, armed with the numbers. Escalating first damages the relationship, and overtime or a contractor spend money before anyone has agreed the trade-off.