PMI-ACP · Domain 2 of 4

PMI-ACP Domain 2: Leadership

Leadership covers how an agile practitioner influences without commanding: empowering the team, guiding problem resolution and conflict, spreading knowledge and agile practices, and keeping everyone pointed at a shared vision. It is a quarter of the exam and full of near-miss options.

Exam weight
25%
Official tasks
6
Estimated questions estimate
~30
Suggested study time estimate
25–35 hrs

About 16 min read Reviewed October 2026

Overview

Leadership has six tasks: empower teams, facilitate problem resolution, promote knowledge sharing, promote agile mindset principles and practices, promote shared vision and purpose, and facilitate conflict management. Together they describe servant leadership, where the practitioner's job is to grow the team's capability and remove obstacles to its self-management rather than assign and inspect work.

Candidates need to know which stance a situation calls for, such as coaching, mentoring, training, facilitating or stepping back, and how to read the level of a conflict before acting. The domain exists because agile teams fail most often through people problems, not tooling. It connects tightly to Mindset, which supplies the values being promoted, and to Delivery, where impediment removal and continuous improvement depend on the leadership behaviors learned here.

How it's tested

Leadership items describe a team member, a team or a stakeholder in difficulty and ask for the BEST, FIRST or NEXT action by the agile practitioner. Read for who owns the decision and how serious the situation has become. The right answer usually helps the team solve the problem itself, intervening more directly only when the scenario signals escalation.

  • Who should solve this?

    A team problem appears, and you choose between solving it yourself, facilitating the team to solve it, or escalating; facilitation usually wins unless the team lacks authority.

  • Read the conflict level

    A disagreement is described, and you diagnose whether it is a problem to solve, a disagreement, a contest, a crusade or a world war, then match the response.

  • Coach, mentor or train

    A team member lacks a skill or confidence, and you choose the development stance that fits: training for missing knowledge, coaching for unlocking their own answers, mentoring for experience sharing.

Reasoning it through

Two developers argue in the daily standup about a design, and both now refuse to review each other's code. Diagnose the level: personal positions and protecting oneself suggest a contest, beyond a simple disagreement. The best response is to meet with both, refocus on shared goals and interests, and facilitate a decision process, rather than ignore it for the team to self-resolve or immediately escalate to their functional manager.

Tasks 6

Official tasks from the PMI outline, in outline order.

2.1 Empower TeamsBuild trust, motivation and capability so the team self-manages.
What it means
Create conditions in which the team can own its goals and decisions: build trust, motivate, coach and mentor, promote collective ownership, apply emotional intelligence, and use self-assessments to grow capability.
What to understand
Servant leadership puts the team's needs first: shield it, remove obstacles, and develop people. Training transfers knowledge, coaching helps someone find their own answer through questions, and mentoring shares the mentor's experience; emotional intelligence (self-awareness, self-management, social awareness, relationship management) lets you read what a person needs.
How it shows up
A team keeps asking the practitioner to make decisions it could make itself, and the best answer coaches the team toward the decision rather than deciding for it.
Common confusion
Treating empowerment as abandonment; empowered teams still get clear goals, boundaries and support.
2.2 Facilitate Problem ResolutionFind root causes and resolve problems quickly and with value.
What it means
Help the team investigate the true cause of a problem, choose the resolution that delivers the most value, and act before the problem grows.
What to understand
Root-cause techniques include the five whys, fishbone (Ishikawa) diagrams and data review. The team should be involved because those closest to the work see causes others miss, and resolution should be time-boxed so analysis does not become its own impediment.
How it shows up
A recurring defect or delay is described, and the best answer runs a team root-cause session before choosing a fix.
Common confusion
Fixing the symptom quickly and calling the problem solved; recurrence is the clue that the root cause is untouched.
2.3 Promote Knowledge SharingCapture, spread and reuse knowledge inside and beyond the team.
What it means
Set up ways for knowledge to move between people and teams, draw on organizational knowledge assets, and protect time for sharing.
What to understand
Tacit knowledge spreads through pairing, mobbing, communities of practice and demos; explicit knowledge lives in wikis, lessons learned and shared repositories. Knowledge silos create bus-factor risk, so cross-training is a risk response as well as a team practice.
How it shows up
Only one person understands a critical component, and the best answer is pairing or rotation to spread knowledge, not more documentation alone.
Common confusion
Assuming a document captures expertise fully; tacit skill transfers best through working together.
2.4 Promote agile mindset principles and practicesRaise awareness of agile values and reinforce agile behavior.
What it means
Help the team and the wider organization understand agile values and principles, encourage continuous improvement, and recognize behavior that reflects them.
What to understand
Adoption spreads through example, education and recognition, not mandate. Practitioners explain the why behind practices, tailor them to context, and celebrate behaviors such as surfacing problems early or collaborating across roles.
How it shows up
Stakeholders or managers misunderstand agile, for instance demanding fixed detailed plans, and the best answer educates them on agile principles and the reasoning behind them.
Common confusion
Enforcing ceremonies by the book and calling it agile; principles matter more than strict adherence to a ritual.
2.5 Promote shared vision and purposeKeep stakeholders and the product aligned to one vision.
What it means
Make sure stakeholders share the same understanding of the product vision, keep the product aligned with organizational goals, and communicate the vision continuously.
What to understand
Tools include a product vision statement, an elevator pitch, a product box exercise and a project or team charter. A clear vision lets the team make local decisions that still serve the goal, and it has to be repeated as people and priorities change.
How it shows up
Team members or stakeholders pull the product in different directions, and the best answer revisits the shared vision with them before reprioritizing features.
Common confusion
Treating the vision as a one-time kickoff artifact rather than something to reinforce throughout the work.
2.6 Facilitate conflict managementDiagnose conflict level and root cause; resolve collaboratively.
What it means
Identify the root cause and intensity of a conflict and promote a resolution the parties reach together.
What to understand
Speed Leas's levels run from 1 (problem to solve) through 2 (disagreement), 3 (contest), 4 (crusade) and 5 (world war); lower levels suit collaboration and consensus, higher levels need the leader to establish safety, separate parties or bring in outside help. Conflict about tasks can be productive; conflict about people is not.
How it shows up
A conflict is described with clues such as personal attacks or taking sides, and you pick the response that fits its level.
Common confusion
Using one approach for every conflict, either always letting the team self-resolve or always stepping in to decide.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Servant leadership

    A leadership style in which the leader serves the team by removing impediments, shielding it from distractions, and growing its capability so it can self-manage.

    Remember
    Serve first, then lead; the leader's success is measured by the team's growth and results.
    Tested as
    It defines the expected stance in nearly every Leadership scenario.
    Trap
    Confusing serving the team with doing the team's work for it.

  • Coaching vs. mentoring vs. training

    Training teaches defined knowledge or skills; coaching uses questions to help someone find their own path; mentoring shares the mentor's experience and advice over time.

    Remember
    Missing knowledge calls for training; unclear choices call for coaching; career or experience gaps call for mentoring.
    Tested as
    The ECO explicitly asks you to distinguish these, so expect a scenario where only one fits.
    Trap
    Choosing coaching for someone who simply has never learned the technique.

  • Emotional intelligence

    The ability to recognize and manage your own emotions and those of others, often modeled as self-awareness, self-management, social awareness and relationship management.

    Remember
    Start with self-awareness; you cannot manage others' reactions while ignoring your own.
    Tested as
    Appears when a team member's behavior changes or when the leader must read non-verbal cues.
    Trap
    Addressing an emotional situation with a process fix only.

  • Levels of conflict (Speed Leas)

    Level 1 problem to solve, 2 disagreement, 3 contest, 4 crusade, 5 world war; language moves from sharing information to protecting self, winning, and finally destroying the other side.

    Remember
    Levels 1 to 3 can usually be worked through with collaboration or negotiation; levels 4 and 5 need the leader to de-escalate and may need outside help or separation.
    Tested as
    Conflict scenarios give language clues so you can diagnose the level.
    Trap
    Trying consensus building at level 5 or heavy intervention at level 1.

  • Five whys

    A root-cause technique that asks why a problem occurred repeatedly, each answer becoming the next question, until a fixable process cause appears.

    Remember
    Stop at a cause the team can act on, and verify it with data where possible.
    Tested as
    The default answer when a recurring problem is described.
    Trap
    Stopping at a person's mistake rather than the system that allowed it.

  • Fishbone (Ishikawa) diagram

    A cause-and-effect diagram that groups possible causes of a problem into categories such as people, process, tools and environment.

    Remember
    Useful when causes may be many and varied; it organizes brainstorming before analysis.
    Tested as
    Appears alongside five whys in problem-resolution scenarios.
    Trap
    Treating every listed cause as confirmed without evidence.

  • Collective ownership

    The whole team shares responsibility for goals, code and outcomes, so anyone can improve any part and success or failure belongs to the team.

    Remember
    It reduces silos and blame and enables swarming on bottlenecks.
    Tested as
    Appears when individuals protect their own tasks or code.
    Trap
    Rewarding individual heroics that undermine team ownership.

  • Communities of practice

    Voluntary groups of people across teams who share a discipline, such as testing or architecture, and meet to share knowledge and improve practice.

    Remember
    They spread knowledge across team boundaries without a reporting line.
    Tested as
    A likely answer for scaling knowledge sharing across several teams.
    Trap
    Making them mandatory status meetings, which kills participation.

  • Product vision statement and elevator pitch

    Short statements of who the product is for, the need it meets, what it is and how it differs from alternatives.

    Remember
    A vision is brief enough for everyone to repeat and use when making local decisions.
    Tested as
    Appears when stakeholders or team members disagree about direction.
    Trap
    Writing a long requirements list and calling it the vision.

  • Delegation boards and decision levels

    Management 3.0 tools that make explicit how much authority the team has on a decision, from tell and sell through consult and agree to advise, inquire and delegate.

    Remember
    Clarifying who decides prevents both micromanagement and confusion.
    Tested as
    Useful when a team is unsure whether it may decide something.
    Trap
    Assuming an empowered team decides everything, including matters outside its authority.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Training vs. coaching vs. mentoring

ConceptMeaningKey differenceCommon trap
Training Structured teaching of defined skills or knowledge Content flows from trainer to learner Using coaching questions when the person lacks the basic knowledge
Coaching Helping someone reach their own solutions through questions and reflection Answer comes from the coachee Giving advice and calling it coaching
Mentoring Ongoing guidance from someone more experienced in a field or role Mentor shares personal experience and advice Expecting a mentor to deliver a formal skills course

Conflict levels and fitting responses

ConceptMeaningKey differenceCommon trap
Level 1: problem to solve Open, fact-based, people share information Collaborate; often the team resolves it alone Intervening heavily in normal work disagreement
Level 2: disagreement Self-protection appears; people talk in general terms Build safety and support the team toward consensus Ignoring growing guardedness
Level 3: contest Winning matters; sides form; personal attacks begin Leader facilitates and may accommodate, negotiate or get factual Expecting easy consensus
Level 4: crusade Parties protect their group and believe the other cannot change Leader de-escalates, uses diplomacy, may separate parties Running a brainstorming session as if trust were intact
Level 5: world war Goal is to destroy the other side Prevent harm; separation or outside help Attempting team-led resolution

Servant leader vs. traditional manager responses

ConceptMeaningKey differenceCommon trap
Servant leader Facilitates, removes impediments, develops people, protects focus Team decides how to do the work Becoming passive when action is needed
Traditional manager Assigns tasks, tracks individuals, decides and escalates Manager decides how work is done Choosing task assignment because it looks decisive

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Decisive leader

    What candidates pick
    The practitioner decides the technical approach to end a team deadlock.
    Why it looks right
    It is quick and unblocks the work.
    Why it's wrong
    Deciding for the team erodes self-management and ownership; facilitating a structured decision, such as fist of five or a time-boxed spike, keeps ownership while still unblocking.

    Clue to watch for The decision is within the team's authority and the conflict is at a low level.

  2. Escalate to the functional manager

    What candidates pick
    Report two quarreling team members to their line manager.
    Why it looks right
    It follows the organizational chain and transfers responsibility.
    Why it's wrong
    Escalation is a last resort; the agile practitioner should first diagnose the conflict level and facilitate resolution with the parties directly.

    Clue to watch for The conflict has not reached the point of harm or entrenched camps.

  3. Let the team sort it out

    What candidates pick
    Stay out of a conflict involving open hostility because agile teams self-organize.
    Why it looks right
    Non-intervention sounds like empowerment.
    Why it's wrong
    At higher conflict levels the team can no longer resolve the issue alone; a servant leader steps in to restore safety and structure.

    Clue to watch for Language shows sides forming, personal attacks, or refusal to work together.

  4. Document the expert's knowledge

    What candidates pick
    Ask the only database expert to write comprehensive documentation.
    Why it looks right
    Documentation seems like a lasting, visible fix.
    Why it's wrong
    Documents capture little tacit skill and take the expert away from work; pairing, rotation or mobbing spreads capability faster and lowers the single-point-of-failure risk.

    Clue to watch for A bottleneck depends on one person's hands-on expertise.

  5. Vision by memo

    What candidates pick
    Email the updated product roadmap to resolve stakeholder disagreements about direction.
    Why it looks right
    It communicates the official direction clearly.
    Why it's wrong
    Disagreement shows a shared vision is missing; the fix is a collaborative session to rebuild shared understanding and tie features to the goal, not a one-way broadcast.

    Clue to watch for Stakeholders each describe a different product or keep reprioritizing in conflicting ways.

  6. Patch and move on

    What candidates pick
    Apply a quick fix to a recurring build failure so the sprint goal is met.
    Why it looks right
    It protects delivery in the short term.
    Why it's wrong
    Recurrence means the root cause remains; facilitating a five whys or fishbone session prevents the next failure and is what the task requires.

    Clue to watch for The scenario says the problem has happened before.

Answer framework

For Leadership scenarios, use these steps to pick the action a servant leader would take.

  1. Identify who owns the decision or problem, and whether the team has the authority and skill to handle it itself.
  2. Diagnose the situation: the root cause of a problem, the level of a conflict, or the specific gap in a person's knowledge, skill or confidence.
  3. Choose the least directive stance that will work, such as asking, coaching, facilitating, training or mentoring, before deciding for others.
  4. Escalate your involvement only when clues show harm, entrenched sides, or a decision beyond the team's authority.
  5. Tie the action back to the shared vision and agile principles, and reject options that assign blame or bypass the team.

Practice question

A new team member struggles to write automated unit tests. The team uses test-driven development, but she has never been taught it and is falling behind. Which development approach should the agile practitioner arrange FIRST?

Want more like this? The PMI-ACP practice test has questions for every domain.

Checklist

0 of 12

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Begin Leadership with servant leadership as the organizing idea, then learn the tools that express it: the training, coaching and mentoring distinction, emotional intelligence, and Speed Leas's conflict levels. These three are the most directly testable pieces, and the conflict levels in particular reward memorizing the language clues for each level.

Next, study problem resolution and knowledge sharing together, since both are about the team building capability: root-cause techniques, pairing and mobbing, communities of practice, and lessons learned. Candidates commonly underestimate Promote shared vision and purpose because it sounds abstract; practice tying a stakeholder disagreement back to a vision statement before any backlog change.

The main skill in this domain is calibrating intervention. For each practice item, ask who owns the decision and how serious the situation is, then pick the least directive action that works. Track your misses by type: too passive or too controlling. Most candidates lean one way consistently, and seeing your pattern fixes many errors.

Afterwards, move to Product, where the shared vision becomes a backlog, and then drill mixed situational sets.

FAQ

How much of the PMI-ACP exam is Leadership?

Leadership is 25% of the exam. Our planning estimate is about 30 of the 120 items, though PMI does not publish per-domain question counts.

Do I need to know Speed Leas's conflict levels by name?

Knowing them is the most reliable way to answer Facilitate conflict management items, because scenarios describe conflict intensity through language clues and the right response depends on the level.

When should the agile practitioner make a decision for the team?

Rarely, and mainly when the decision is outside the team's authority, the situation is harmful, or the team is stuck in a way facilitation cannot resolve. Otherwise, facilitate the team to decide.

What is the difference between coaching and mentoring on the exam?

Coaching helps a person find their own answers through questions; mentoring shares the mentor's own experience and advice. Training differs from both because it teaches a defined body of knowledge or skill.

Is Leadership only about the team, or stakeholders too?

Both. Promote shared vision and purpose and Promote agile mindset principles and practices often involve sponsors, managers and other stakeholders who need education or alignment.

How does Leadership relate to Delivery?

Delivery's impediment, risk and improvement tasks rely on the facilitation and root-cause skills taught here; Leadership explains how to involve the team, and Delivery explains what to measure and remove.

How long should I study Leadership?

Our planning estimate is 25–35 hours within a 120-hour plan, with most of it on situational practice questions rather than reading.

Other Project Management certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 2 knowledge

You have covered servant leadership, development stances, root-cause problem solving, shared vision and conflict levels. Test whether you can calibrate your intervention correctly under exam conditions.

Take the PMI-ACP practice test Check your PMI-ACP readiness

Keep going