Domain I (People) is 42% of the PMP exam. Task 1.1 (Manage conflict) is the most tested task in the domain. If you’re weak on conflict-management scenarios, your overall score drops regardless of how strong you are on Process and Business Environment.
Five scenarios cover 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 and recommend the right conflict resolution approach
Each question has a rationale for every answer option. 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 retrospective, two senior developers start arguing. The fight is about the team’s decision to adopt a new CI/CD tool. One developer feels the decision was rushed. The other feels the objection came too late. Other team members grow quiet. 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 disagreement about process timing and tool fit, and ask each developer what they need 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 handling. The conflict is visible and active. It is Stage 3 (Contest) in Speed Leas’ model. Per PMBOK 7, the PM’s job is to create safety by naming the conflict and giving each party a voice before seeking 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 without resolution. PMI wants you to address conflict where it surfaces. 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 leadership. It shames the developers and closes the discussion. The agreement may become relevant later. But leading with it treats the conflict as a rule violation rather than a real technical and process disagreement.
Why D is a trap
Escalation at Stage 3 is premature. PMI expects the PM to facilitate first. Escalate only after team-level resolution has failed. Escalating this fast undermines Scrum’s self-organization principle. It also signals the PM cannot handle normal conflict.
Question 2: Cross-team defect dispute (Hard, Predictive)
A QA functional manager has complained three times this month. The complaint: a programmer on your project ignores defect reports. In your 1:1, the programmer says the QA lead is weaponizing defects to reclaim capacity for a competing project. 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 agree on defect-triage rules C. Review the defect data yourself to determine whether the QA lead’s reports are valid before doing anything else D. Tell the functional manager that issues between their staff are theirs to resolve, not yours
Correct answer: C
Before intervening or escalating, PMI expects the PM to analyze context. Here context means data. If the defects are real, this is a performance issue. If they are weaponized, this is a resource-contention issue. The right response differs. Jumping to facilitation without data risks siding with whoever argues better.
Why A is a trap
Escalating to the sponsor before you analyze the conflict is premature. Sponsors handle genuine priority conflicts, not normal team friction. You would also be escalating without data. That damages your credibility.
Why B is a trap
Facilitating too early is a trap. If the defects are real, facilitation gives the programmer a stage to deflect. Gather context before facilitating when data is in dispute.
Why D is a trap
This is abdication. The programmer and QA lead share a functional manager, but the conflict is hurting your project. PMI expects the PM to own any conflict that impacts the project, regardless of who reports to whom.
Question 3: Framework disagreement (Easy, Hybrid)
Two team members disagree on which JavaScript framework to adopt for a new internal tool. The debate has been respectful but unresolved for a week. It is delaying the design spike. Both frameworks would work technically.
What resolution approach is MOST appropriate?
A. Compromise: adopt parts of both frameworks in a hybrid architecture B. Collaborate: facilitate a session where both members present trade-offs and the team decides together 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 will support
Correct answer: B
This is a low-stakes technical conflict that is respectful but unresolved. That is the textbook setup for Collaborate/Problem-Solve. It is PMI’s highest-value conflict technique. Collaboration surfaces trade-offs, teaches the team, and produces a decision the team owns. PMI considers it the ideal default when time permits.
Why A is a trap
A hybrid architecture is technically harmful. Mixing JS frameworks creates maintenance debt. Compromise works for positional negotiations, not design decisions where one architecture is coherent and two are brittle.
Why C is a trap
Force is a last resort for urgent decisions when the team cannot agree. Nothing here is urgent. The delay is one week and both options work. Forcing would undermine team ownership. PMI discourages it in this scenario.
Why D is a trap
Smooth dismisses the issue without resolving it. The team is stuck. Saying either is fine does not unblock them. It abandons them. Smoothing is for low-stakes 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 fought over scope for three sprints. The PO filed a formal complaint. The developer told you privately they may leave 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 talk, before rescheduling C. Hold the sprint review but open it with a note that the team has been under tension D. Meet with HR first to document the situation before taking any action
Correct answer: B
This is Stage 4-5 conflict. Normal facilitation will not work here. PMI expects the PM to triage by severity. When a team member may leave, the project risk exceeds the cost of a delayed sprint review. Do separate 1:1s first to hear each side. Then hold a joint conversation. That is PMI’s standard pattern for escalated conflict. You can reschedule the sprint review. You cannot replace a developer who quits.
Why A is a trap
Proceeding exposes the conflict to stakeholders. They will notice. It signals you are not addressing it. And it misses the window before the developer decides to quit.
Why C is a trap
Airing internal conflict during a stakeholder ceremony violates PMI’s principle. Stakeholders are audience, not arbiters. This would embarrass the team and damage the PO-developer relationship further.
Why D is a trap
Going to HR first is over-escalation. HR becomes relevant after PM-level intervention fails, or if the conflict becomes harassment. The formal complaint informs your approach. It does not replace it.
Question 5: Covert distributed-team conflict (Medium, Predictive)
Your team is spread across three time zones. Over the past month you notice a pattern. Decisions made in the morning stand-up (mostly Europe-based) get re-litigated in the afternoon stand-up (mostly Americas-based). Team members never name the disagreement openly. Decisions quietly reverse.
What type of conflict is this, and what should the PM do FIRST?
A. Latent conflict: do nothing yet, it has not 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 are seeing D. Manifest conflict: issue a decision-making RACI so it is clear who has authority
Correct answer: C
The conflict is FELT. People act on it by reversing decisions, but no one has named it openly. This is Speed Leas’ Stage 2. The PM’s role is to surface what is beneath the surface without escalating it. Name the pattern neutrally: “I noticed decisions keep reversing. What is going on?” This invites the team to make the felt conflict visible. That is a prerequisite for resolution. You cannot pick a solution before you diagnose.
Why A is a trap
Latent conflict is tension that has not yet affected behavior. Here, decisions are actively reversing. Behavior is already affected. Doing nothing lets the pattern calcify.
Why B is a trap
One stand-up may become the right fix after diagnosis. But acting on it now assumes the problem is time-zone friction. It could be trust, authority ambiguity, or cultural differences. You are solving before you have listened.
Why D is a trap
A RACI is also a structural fix without diagnosis. It may help, but giving authority rules to a team with hidden conflict often makes it more hidden. Fix the interpersonal issue before the structural one.
How to use these
If you got 5/5 right, your conflict mental model matches PMI’s. Move to the next Domain I task.
If you missed one, read the rationale for the option you picked. What did your wrong pick assume about PMI? That assumption will appear again. 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.