Domain I (People) is 42% of the PMP exam, and Task 1.1 (Manage conflict) is the most frequently tested task in the domain. If you’re weak on conflict-management scenarios, your overall PMP score gets dragged down no matter how strong you are on Process and Business Environment.
Below are five scenarios covering all three enablers of Task 1.1 from the PMI Examination Content Outline:
- Enabler 1: Interpret the source and stage of the conflict
- Enabler 2: Analyze the context for the conflict
- Enabler 3: Evaluate/recommend/reconcile the appropriate conflict resolution solution
Each question has a rationale for every answer option. Click through and see why your specific wrong pick was wrong, not just why the correct answer is correct.
Question 1: Active retrospective conflict (Medium, Agile)
During a Scrum team retrospective, two senior developers begin raising their voices at each other over the team’s decision to adopt a new CI/CD tool. One developer feels the decision was rushed; the other feels the objection is coming too late. Other team members grow quiet and avoid eye contact. The disagreement is blocking the retrospective’s action items.
What should the project manager do FIRST?
A. Adjourn the retrospective and reschedule once tempers have cooled B. Acknowledge the tension, name the underlying disagreement about process timing and tool fit, and ask each developer to share what they need to feel heard before the team continues C. Remind the team of the working agreement they signed during Sprint 0, which prohibits personal attacks D. Escalate the disagreement to the engineering manager so a neutral party can arbitrate
Correct answer: B
This is stage-appropriate conflict interpretation. The conflict is visible, active, and affecting the team. Stage 3 (Contest) in Speed Leas’ model. The PM’s job per PMBOK 7’s emphasis on servant leadership is to create psychological safety by naming the conflict and giving each party voice before attempting resolution. Action items without resolution will fail anyway.
Why A is a trap
Adjourning is avoidance. It moves conflict from Stage 3 back to Stage 1 (where it festers) without resolution. PMI’s philosophy: address conflict where it surfaces, don’t delay. You would only adjourn if there were safety concerns or a need for deep preparation, neither applies here.
Why C is a trap
Citing the working agreement is rules-based enforcement, not facilitative leadership. It shames the developers and closes the discussion. The agreement may become relevant later, but leading with it treats the conflict as a behavioral violation rather than a legitimate technical and process disagreement.
Why D is a trap
Escalation at Stage 3 is premature. PMI expects the PM to facilitate first and escalate only when team-level resolution has been attempted and failed. Escalating this quickly undermines the team’s self-organization (a core Scrum value) and signals the PM cannot handle normal conflict.
Question 2: Cross-team defect dispute (Hard, Predictive)
A functional manager from QA has complained three times this month that a programmer on your project is unresponsive to QA defect reports. The programmer reports to the same functional manager. In your 1:1, the programmer says the QA lead is “weaponizing” defects to reclaim capacity for a competing project the QA lead owns. Both escalate to you separately.
What should the project manager do NEXT?
A. Ask the sponsor to clarify priority between this project and the QA lead’s competing project B. Facilitate a joint meeting between the programmer and QA lead to surface the underlying resource contention and agree on defect-triage rules C. Review the defect data yourself to determine whether the QA lead’s reports are legitimate before taking any other action D. Tell the functional manager that interpersonal issues between their staff are theirs to resolve, not yours
Correct answer: C
Before intervening socially (B) or escalating (A), PMI expects the PM to analyze the CONTEXT, which here is a data question. If the defects are legitimate, the conflict is a performance issue; if they’re weaponized, it’s a resource-contention issue. The correct response is different in each case. Jumping to facilitation without data risks siding with the party who speaks more persuasively.
Why A is a trap
Escalating to the sponsor before analyzing the conflict yourself is premature. Sponsors handle genuine priority conflicts, not normal team friction. You’d also be escalating without data, which damages your credibility with the sponsor.
Why B is a trap
Facilitating too early is a common trap. If the defects are legitimate, facilitation becomes a forum for the programmer to deflect accountability. Context-gathering must precede facilitation when data is disputed.
Why D is a trap
This is abdication. Even though the programmer and QA lead share a functional manager, the conflict is actively harming YOUR project. PMI expects the PM to own project-impacting conflict regardless of reporting lines.
Question 3: Framework disagreement (Easy, Hybrid)
Two team members disagree about which JavaScript framework to adopt for a new internal tool. The disagreement has been respectful but unresolved for a week, delaying the design spike. Both frameworks would technically work.
What resolution approach is MOST appropriate?
A. Compromise, adopt parts of both frameworks in a hybrid architecture B. Collaborate, facilitate a working session where both members present trade-offs, and the team decides together using agreed criteria C. Force, as the PM, make the decision yourself to remove the blocker D. Smooth, tell both that either framework is fine and whichever they pick, you’ll support
Correct answer: B
This is a low-stakes, technical, unresolved-but-respectful conflict, textbook conditions for Collaborate/Problem-Solve, the highest-value PMI conflict resolution technique. Collaboration surfaces trade-offs, teaches the team, and produces a decision the team owns. PMI considers this the ideal default approach when time permits.
Why A is a trap
Compromise (a hybrid architecture) is technically harmful here, mixing JS frameworks creates maintenance debt. Compromise is appropriate for positional negotiations, not technical design decisions where one architecture is coherent and two are brittle.
Why C is a trap
Force (Direct/Dictate) is a last-resort technique for urgent decisions when the team cannot agree. Nothing about this scenario is urgent, the delay is one week, both options work. Forcing would undermine team ownership and is PMI-contraindicated.
Why D is a trap
Smooth (Accommodate) dismisses the disagreement without resolving it. The team is already stuck, so “either is fine” doesn’t unblock them, it abandons them. Smoothing is reserved for low-stakes, relationship-preservation situations where the technical answer truly does not matter.
Question 4: High-stakes sprint-review conflict (Hard, Agile)
A product owner and a lead developer have been in escalating conflict over scope for three sprints. The PO has filed a formal complaint. The developer has told you privately that they are considering leaving the company. You have a sprint review tomorrow.
What is the BEST course of action?
A. Proceed with the sprint review as planned, then address the conflict separately after B. Cancel the sprint review, hold an urgent 1:1 with each party, then a joint conversation, before rescheduling the review C. Hold the sprint review as planned but open it with an acknowledgement that the team has been under tension, creating space for the stakeholders to see the conflict D. Meet with HR first to document the situation before taking any action
Correct answer: B
This is a Stage 4-5 conflict (formal complaint + retention risk), past the point where normal facilitation works. PMI expects the PM to triage by severity: when a team member is considering leaving, the project risk exceeds the cost of a delayed sprint review. Separate 1:1s (to understand each side without performance) followed by joint conversation is the PMI-standard escalated-conflict pattern. The sprint review can be rescheduled; a lost developer cannot.
Why A is a trap
Proceeding exposes the conflict to stakeholders (who will notice) and signals that you’re not addressing it. It also misses the window before the developer decides to leave.
Why C is a trap
Airing internal team conflict during an external-facing stakeholder ceremony violates PMI’s “wash your dirty laundry privately” principle. Stakeholders are audience, not arbiters. This would embarrass the team and further damage the PO-developer relationship.
Why D is a trap
Going to HR first, before attempting any PM-led resolution, is over-escalation. HR becomes appropriate after PM-level intervention fails or if the conflict crosses into harassment/policy territory. The formal complaint is an input to your intervention, not a substitute for it.
Question 5: Covert distributed-team conflict (Medium, Predictive)
Your project team is distributed across three time zones. Over the past month, you’ve noticed a pattern: decisions made in the morning stand-up (attended mostly by Europe-based team members) are routinely re-litigated in the afternoon stand-up (attended mostly by Americas-based team members). Team members rarely name the disagreement openly; instead, decisions quietly reverse.
What type of conflict is this, and what should the PM do FIRST?
A. Latent conflict, do nothing yet; it hasn’t surfaced B. Perceived conflict, schedule a single team-wide stand-up so everyone attends the same meeting C. Felt conflict, call out the reversal pattern in the next stand-up and ask the team what they’re seeing D. Manifest conflict, issue a decision-making RACI so it’s clear who has authority
Correct answer: C
The conflict is FELT (people are acting on it, reversing decisions, but it hasn’t been openly discussed). This is Speed Leas’ Stage 2. The PM’s role at this stage is to surface what’s beneath the surface without escalating it. Naming the pattern neutrally (“I’ve noticed decisions are reversing, what’s going on?”) invites the team to make the felt conflict manifest, which is a prerequisite to resolution. Solutions (B, D) cannot be chosen intelligently before diagnosis.
Why A is a trap
This is not latent. Latent conflict is underlying tension that has not yet affected behavior. Decisions are actively being reversed, behavior is already affected. Doing nothing allows the pattern to calcify.
Why B is a trap
The structural fix (one stand-up) may become the right answer after diagnosis, but implementing it now assumes the problem is time-zone friction. It might actually be trust, authority ambiguity, or cultural communication differences. You’re solving before you’ve listened.
Why D is a trap
A RACI is also a structural solution without diagnosis. It may help, but issuing authority rules to a team with covert conflict often makes the conflict more covert, not less. Address the interpersonal dynamic before the structural one.
How to use these
If you got 5/5 right, your conflict management mental model matches PMI’s. Move to the next Domain I task.
If you missed one, go back and read the distractor rationale for the option you picked. What did your wrong pick assume about PMI philosophy? That assumption will show up again on the exam. Name it so you can catch it.
If you missed three or more, you likely have one of the three major PMP biases - read the diagnostic here.
Want 500 more questions like these, each with per-option rationales and a drill targeting your specific miss pattern? PassCoach.ai is in beta waitlist, first 100 signups get lifetime access at $99 instead of $29/mo.