Which ACP section wrecks everyone? For me it was the mindset questions
So I sat the ACP last Thursday and I'm still kind of decompressing. Passed, barely felt like it in the moment, but I want to put this out there because before my exam I read a hundred of these threads and most of them just said "study the Agile Manifesto lol." Not helpful. The part that actually tripped me up wasn't the math or the formulas or any of the tooling questions. It was the Agile Principles and Mindset domain. That whole chunk where they give you a squishy scenario and four answers that all sound reasonable, and you're supposed to pick the "most Agile" one. Brutal.
Here's the thing nobody tells you. The mindset questions aren't testing whether you memorized the twelve principles. They're testing whether you can think like someone who actually lives them, which is a totally different skill. I kept picking answers that were technically correct but a little too command-and-control, and the "right" answer was always the one that pushed decisions to the team or favored conversation over documentation. Once that clicked for me my mock scores jumped. I'd been doing okay on estimation and metrics for weeks but the soft stuff kept dragging me under.
What finally helped was drilling scenario questions until the pattern got into my bones. I ran through this free acp agile principles and mindset questions and answers set probably four or five times, and reading the explanations mattered way more than the score. You're not memorizing, you're recalibrating your gut. The first pass I got like 60%. By the end I could read the stem and basically feel which answer they wanted before I even hit the options.
If you're early in your exam prep, my honest advice is don't leave the mindset domain for last because it "seems easy." That's the trap. The mechanical stuff, velocity, burndown, EMV, all that, you can cram in a weekend. The mindset thinking takes reps over time. I treated every practice test as a diagnostic, not a grade, and went back through every wrong answer to figure out why my instinct was off. Tedious but it works. You can find a full-length agile certified practitioner test to simulate the real timing too, which I'd do at least twice before the real thing.
Anyway. If you're stuck on the same wall I was, you're not dumb and you didn't pick the wrong cert. Your brain just defaults to traditional PM thinking and the exam punishes that. Reframe it, drill the scenarios, read every explanation. The math will take care of itself.
Quick update for anyone tracking their progress in here. I hit 78% on a full mock yesterday which is the first time I've cracked 75, and honestly the mindset and value-driven stuff is still where I bleed points. Knowledge area questions I'm fine with. It's the "what does the agile coach do RIGHT NOW in this situation" ones that get me every time. I've been grinding through these free acp value driven delivery questions because that domain wrecked my first two attempts and I needed reps, not just rereading the manifesto for the tenth time.
Plan is to sit the real thing in about three weeks. I want two more mocks above 75 before I book it, because last time I went in off one good practice score and it wasn't enough. If you're struggling with the mindset section you're not alone, it's not just you being slow. Drill the situational ones over and over and it does start to click.
Quick update for anyone lurking this thread like I was. I sat a full practice test last night and pulled a 78%, which is the first time I've cracked the 70s on the timed ones. The mindset and "what would the agile coach do" questions are still where I bleed points, exactly like you said. Knowing the Manifesto cold didn't save me there because the answers all sound right until you really sit with them.
I'm planning to book the real ACP for the last week of this month, give myself maybe ten more days. My plan is to stop grinding new material and just keep redoing the scenario questions I get wrong until the reasoning sticks. If I'm honest the content isn't the hard part anymore, it's trusting my gut under the clock. We'll see if past me regrets writing this so confidently.
Passed mine almost two years back now and the mindset stuff still sticks with me, because you're right — it's the part nobody can really hand you a flashcard for. What finally clicked for me was realizing the exam isn't testing whether you know the Manifesto, it's testing whether you've internalized it enough to pick the "less wrong" answer when two options both sound reasonable. The classic trap is the question where one answer is "go talk to the team" and another is "escalate to the sponsor" or "update the plan." Almost always the agile-correct move is the one that pushes the decision toward the people doing the work and favors a conversation over a document. Once I started reading every situational question through that lens, the mindset domain went from my worst to my most reliable.
The thing I wish someone had told me: stop trying to memorize the 12 principles word for word and instead drill the tradeoffs. Responding to change vs following a plan, working software vs documentation — the exam loves to make you choose between two genuinely-okay options where one just leans a little more agile. That's the whole game in that section.
Hindsight take on what actually mattered for me long term? Almost none of the lean metrics trivia. I couldn't tell you the exact cumulative flow diagram question I sweated over. But the mindset reps — defaulting to transparency, swarming a problem instead of assigning blame, pulling stakeholders in early — that's the stuff I actually use at work, and funnily enough it's also what the exam weights heaviest. So if you're studying and short on time, over-index there. It pays off twice.
The mindset stuff got me too, and honestly what finally clicked was treating them less like knowledge questions and more like "who makes this decision" questions. Almost every situational one I saw was testing whether you'd let the team self-organize or whether you'd swoop in and fix it yourself. So I made a little filter: if an answer has the Scrum Master or coach solving the problem, assigning the work, or escalating to a manager, it's almost always wrong. The right answer usually puts it back on the team or makes the impediment visible. Sounds obvious typed out, but under pressure your gut wants to pick the "take charge" option because that's what feels responsible everywhere except agile.
Concrete thing that helped me drill it: I rewrote maybe 40 practice questions into a two-column sheet — left side the situation, right side just the single word for where the decision belonged (team, PO, retro, daily standup, "make transparent"). Not the full answer, just the destination. After doing that for a few days I stopped reading all four options carefully and instead asked myself the destination first, then matched it. Cut my second-guessing way down. The exam loves giving you two answers that are both "agile-ish" and the difference is timing — like do you raise it now in the daily standup or park it for the retro. Knowing the ceremony's actual purpose is what splits those.
One more — pay attention to the questions where nothing is broken yet and they're asking what you'd do "first." Those trip people because the instinct is to act. A lot of the time the most agile first move is to gather information or make something visible before changing anything. Caught me off guard at least three times.
Related Discussions
- Failed the CSPO — what to do differently the second time5 replies
- Did getting the Disciplined Agile Coach cert actually move the needle on your job search?5 replies
- How close are AAC practice tests to the real exam? My honest review5 replies
- Deep dive on study guide for the DA — tips from someone who almost failed it5 replies
- AAC exam mistakes I wish someone had warned me about5 replies