PMI-ACP PMI Agile Certified Practitioner Exam Topics and Questions

This is the heaviest topic on the exam, and PMI means it. You're being tested on whether you think like an agile practitioner or like someone who read a book about agile. The difference shows up in scenario questions where a team is stuck, a stakeholder is unhappy, or a process isn't working. The right answer reflects the values behind the framework, not the framework itself.

– Experimentation, learning and the agile value system

Experimentation means building something testable early, not waiting for a complete picture. You validate both the solution and whether anyone actually needs it, which are separate questions. The agile mindset tasks expect you to apply values and principles in context, not recite them. Complexity theory appears here because agile practitioners classify problems before choosing an approach. You'll see Cynefin, Stacey Matrix, and complex adaptive systems used to decide whether a situation calls for agile at all. Suitability tools help you interpret whether the environment, team, or product fits an agile model, and you're expected to integrate models based on what the scenario needs, not what the organization prefers.

– Team environment, collaboration and transparency

Forming a high-performing team starts with a shared vision and working agreements. Retrospectives feed improvements back into how the team operates. Collaboration practices break down silos, and you're expected to commit to team decisions even when you disagreed during the discussion. Tailoring the agile approach depends on evaluating the team's understanding, which changes as they mature. Inter-team coordination models like scrum of scrums or team of teams appear when multiple teams need to align. Transparency means making status, progress, risks, and impediments visible to everyone through information radiators and feedback loops. Communication strategies differ for co-located and distributed teams, and the exam tests whether you can choose the right one.

– Psychological safety and feedback

Psychological safety is built by promoting objectivity over blame, encouraging dialogue instead of debate, and soliciting constructive feedback that people act on. Challenging the status quo is a sign of a healthy team. Shortening feedback loops means involving stakeholders from day one, maximizing value within a timeframe, and using techniques like design thinking and lean startup to test assumptions faster. The exam expects you to recognize when a feedback loop is too long and know what to do about it.

– Embracing change and adaptation

A growth mindset responds to change instead of resisting it. Process adaptation means adjusting when requirements and priorities shift. Encouraging cross-skills turns specialists into generalizing specialists who can move where the team needs them. Adapting to product needs based on learning and feedback is continuous, and the exam tests whether you default to flexibility or control when a scenario presents both options.

How Mindset is tested

At 28 percent, this topic drives more than a quarter of your score. Items present a scenario where something is going wrong and ask what you do next. The trap is picking the answer that sounds organised or risk-averse instead of the one that reflects agile values. You'll see complexity theory scenarios where you must classify a situation using Cynefin or Stacey Matrix, then choose an approach that matches. Psychological safety items describe a team behaviour and ask what it signals or how you respond. Transparency questions test whether you default to reporting up or radiating out. Feedback loop items give you a timeline and ask where to intervene. Change scenarios contrast a growth mindset response with a defensive one, and the wrong answer often sounds reasonable if you're thinking in waterfall terms. Candidates lose marks by choosing the safe-sounding option over the agile one.

Leadership in agile terms is about enabling the team, not directing it. This topic weighs almost as heavily as Mindset, and it focuses on how you create the conditions for a team to solve its own problems. The cost comes when you default to telling instead of coaching, or when you solve a conflict yourself instead of facilitating a collaborative resolution.

– Empowerment, trust and emotional intelligence

Establishing trust means enabling transparent communication, which is a deliberate choice about how information flows. Motivating team members to experiment or take risks requires an environment where failure is treated as learning. Coaching and mentoring are different from training, and the exam expects you to know when each applies. Emotional intelligence techniques support the team, increase empathy, resolve conflict, and enable positive influence. You interpret non-verbal cues during team interaction and use self-assessment tools to help teams develop their capabilities. Collective ownership of goals means the team owns the outcome together, and you're tested on whether you promote that or undermine it by assigning individual accountability for shared work.

– Problem resolution and knowledge sharing

Facilitating problem resolution starts with root cause analysis using techniques like Ishikawa. You determine resolution strategies with the team, not for them, and you ensure problems are resolved in a timely manner without taking over. Knowledge sharing requires creating an environment to capture and share what the team learns through retrospectives, lessons learned, and communities of practice. Leveraging organisational knowledge assets means pulling in learning from other initiatives, people, and processes. Allocating time for knowledge sharing is explicit, because without it teams skip the step under delivery pressure.

– Vision, agile behavior and conflict

Promoting agile mindset principles and practices means creating awareness around values and principles, fostering continuous improvement, and recognising and celebrating agile behavior when you see it. Promoting shared vision and purpose requires defining a common understanding with all stakeholders, ensuring the product stays aligned to vision and organisational goals, and continuously communicating both. Conflict management starts by identifying the root cause and level of the conflict, then promoting a collaborative approach to solve it. The exam tests whether you step in to resolve or step back to facilitate, and the agile answer is almost always the latter.

How Leadership is tested

Leadership items give you a team in a specific situation and ask what you do. The trap is choosing the answer where you solve the problem yourself instead of enabling the team to solve it. Empowerment scenarios contrast coaching, mentoring, and training, and you lose marks if you confuse them. Emotional intelligence questions describe a team dynamic and ask what it signals or how you respond, often testing whether you interpret non-verbal cues correctly. Problem resolution items present a symptom and ask whether you address it directly or investigate the root cause first. Knowledge sharing scenarios test whether you allocate time for it or expect it to happen in spare moments. Vision and purpose items ask how you maintain alignment when priorities shift. Conflict questions give you a disagreement and ask whether you resolve it, mediate it, or facilitate a collaborative solution. The wrong answer usually involves you taking control.

Product work is where agile theory meets stakeholder expectations. You're refining a backlog, managing increments, visualising work, and delivering value, all while keeping the customer involved. This topic is lighter than Mindset or Leadership, but it punishes you if you treat the backlog as a static plan or if you measure output instead of value.

How Product is tested

Backlog refinement items test whether you clarify and decompose with the team or do it alone, and whether you prioritise with the customer or for them. Collective sizing techniques appear, and you need to know when to use them. Increment management scenarios ask whether the increment aligns with business priorities and whether you demonstrate it for early feedback or wait until it's polished. Value delivery questions define success criteria upfront, including sustainability, security, privacy, regulatory, and compliance concerns. The exam expects you to ensure value increments are optimised and that targeted results like customer satisfaction or sales increases are achieved. Visualisation items test whether you educate the team on techniques, establish a process to update the data, and continuously share information. Candidates lose marks by choosing the answer that protects the plan over the one that adapts to feedback, or by measuring velocity when the question is asking about value.

Delivery ties with Mindset as the heaviest topic. It's where you demonstrate that agile practices actually work: seeking feedback, managing metrics, removing impediments, eliminating waste, improving continuously, engaging customers, and optimising flow. The exam tests whether you default to control or to adaptation when something goes wrong.

– Feedback, metrics and customer engagement

Seeking early feedback means evaluating customer satisfaction, delivering work in small increments, and collecting and incorporating stakeholder feedback on a regular basis. Managing agile metrics starts with determining which metrics suit a given audience, then radiating them across that audience. You review and analyse metrics, then use the insights for decision making. Actively engaging customers means identifying and analysing their needs, validating that iteration deliverables meet acceptance criteria, and encouraging collaboration between customer and team. The exam expects you to involve the customer throughout, not just at the handoff.

– Impediments, risk and waste

Managing impediments and risk means proactively identifying them, engaging the team to find the most appropriate course of action, prioritising removal and mitigation activities, monitoring and controlling them, and using lessons learned to avoid recurrence. Recognising and eliminating waste starts by visualising the end-to-end flow of value in the system, distinguishing value-added from non-value-added activity. You use metrics, tools, and feedback loops to identify waste, prioritise waste reduction activities, and iterate on both identification and reduction. The exam tests whether you treat waste as inevitable or as something to eliminate systematically.

– Continuous improvement and flow optimisation

Performing continuous improvements means obtaining metrics and feedback to drive them, implementing improvement actions, and evaluating the effectiveness of process improvement. It's a cycle, and the exam expects you to close the loop by checking whether the improvement worked. Optimising flow means limiting work-in-progress at all levels, shielding the team from interruptions by creating team interfaces, and using metrics to analyse and improve flow. WIP limits are a lever, and the exam tests whether you apply them or let the team take on everything at once.

How Delivery is tested

Delivery scenarios describe a team delivering work and ask what you do when feedback is negative, when a metric shows a problem, when an impediment blocks progress, when waste is visible, when an improvement fails, when a customer disengages, or when flow stalls. The trap is choosing the answer that sounds like project management instead of agile delivery. Feedback items test whether you deliver in small increments or wait for a complete feature. Metrics questions ask which metric suits the audience and whether you radiate it or report it up. Impediment and risk scenarios test whether you engage the team to solve it or solve it yourself. Waste items ask whether you visualise the flow or assume you know where the waste is. Continuous improvement questions test whether you evaluate the effectiveness of the change or move on to the next one. Customer engagement scenarios ask whether you validate against acceptance criteria or assume the work is done. Flow optimisation items test whether you limit WIP or let the team self-organise around an overload. Candidates lose marks by choosing the answer that maintains control over the one that enables the team to adapt.