Okay so I've been going back and forth on this for weeks and I finally just called PMI directly to get a straight answer. The passing score for the DA isn't publicly disclosed — PMI uses a psychometric scaling process, so there's no fixed percentage like "70% and you're in." What they do is set a cut score based on item difficulty across the entire exam pool. Basically you're not competing against other test takers, you're being measured against a standard. That said, from what I've heard from people who've recently sat for it, you want to be consistently hitting somewhere in the 70-75% range on your practice materials before you even think about booking.
I spent a lot of time with the da agile frameworks and methodologies section because honestly that's where I kept bleeding points. The toolkit stuff is memorizable but the situational questions — the ones where four answers all sound reasonable — those will wreck you if your conceptual understanding isn't solid. My exam prep strategy shifted pretty hard toward understanding WHY disciplined agile recommends certain approaches in certain contexts rather than just what the approach is called.
The breakdown I was working with: roughly 50% of questions center on DA principles and mindset, around 30% on applying the toolkit in real scenarios, and the remaining 20% covers hybrid and enterprise-level stuff. That's not official, just what I triangulated from a few different sources. So if you're weak on the situational application questions, that 30% chunk is where you're actually losing the most ground relative to the cut score — not the definitions.
One thing that genuinely helped me calibrate was using the certified disciplined agile test practice test format as a benchmark rather than just drilling questions. Like, I'd do a full timed session, review every wrong answer cold, then revisit those topics in the book before running another session two days later. It's slower but you actually see your weak spots compound or resolve instead of just grinding through questions and feeling productive without improving.
If you're in that 65-68% plateau on practice tests and feeling stuck, don't just do more questions — that's the trap. Dig into the language PMI uses for the options you keep getting wrong. There's usually a pattern, and once you see it, your score jumps fast.
Just passed mine last month so this thread is hitting close to home. Everything you said about the psychometric scaling tracks with my experience — I went in expecting to hit some magic number and came out realizing that's just not how it works. PMI's whole "Above/Near/Below Target" breakdown is what you're actually shooting for, and getting Above Target in even one or two domains can carry you if you're borderline somewhere else.
The one thing that made a tangible difference for me was drilling scenario questions specifically in the disciplined agile layer model and how the choose-your-WoW philosophy applies in practice. A lot of the questions aren't really testing whether you know definitions — they're testing whether you understand *why* DA gives teams flexibility to adapt their approach. Once I shifted my prep to focus on reasoning through trade-offs rather than memorizing the toolkit, my practice scores jumped. That felt like the actual unlock.
Also don't underestimate the hybrid agile stuff. I expected more pure Scrum territory and got way more questions about blending approaches across teams and at scale. If you're coming from a pure SAFe or Scrum background, carve out dedicated time there.
What finally got me over the hump wasn't taking more practice tests, it was changing how I reviewed them. I used to just check my score, feel bad, and move on. Total waste. Now every time I miss a question I force myself to write out why each wrong answer is wrong, not just why the right one is right. It's slower, sure. But you start seeing the patterns in how they build distractors, and suddenly questions you've never seen before feel familiar because you recognize the trap they're setting.
The section that taught me this the hard way was the da security architecture network defense stuff. I kept picking answers that were technically true but didn't actually address the scenario. Once I started asking "okay, why is this one wrong here specifically" instead of memorizing correct answers, my scores jumped like 15 points. Since PMI scales the scoring anyway and nobody knows the exact cutoff, you can't game it with memorization. You just have to actually get the reasoning down.
One thing that actually helped me figure out where I stood was treating the DA toolkit like a decision framework rather than a vocabulary list. Instead of just memorizing what Guided Continuous Flow or team self-organization means in isolation, I'd pick a scenario — like "your team is transitioning from Scrum and hitting blockers with WIP limits" — and walk through which DA strategies I'd apply and why. Forced me to internalize the reasoning, not just the definitions.
The psychometric scaling thing is real and honestly kind of freeing once you accept it. You're not chasing a number, you're demonstrating judgment across the competency areas. So I stopped tracking "percentage correct" on practice sets and started asking which categories I was getting wrong and whether I understood the DA mindset behind the right answer. A da practice test helped a lot here — the explanations on the wrong answers were where I learned the most, not the score at the end.
Also: don't sleep on the Choose Your WoW! book for the sections on context sensitivity. PMI leans hard into situational judgment and that book basically explains why DA doesn't have one-size-fits-all answers — which is exactly the logic the exam tests.
Failed my first attempt back in November and honestly it wrecked me for a bit. I thought I was prepared — I'd gone through the handbook, done a bunch of flashcards, felt pretty solid on the concepts. But when I saw "did not pass" I had no idea where I'd actually fallen short because PMI doesn't give you a detailed breakdown, just those broad proficiency indicators. That vague feedback is brutal when you're trying to figure out what to fix.
What I changed for round two was shifting away from memorizing DA terminology and focusing more on how the tiers interact in practice — like when it actually makes sense to move from a team-level layer up to program or enterprise, and why. The exam cares a lot about situational judgment, not just "what does CALMR stand for." I also drilled way more scenario-based questions instead of definition-style ones. That shift felt significant.
The psychometric scaling thing you mentioned is real, and I think it messed with my head before my first attempt. I kept chasing a number — 70%, 75%, whatever — when the actual goal is demonstrating consistent proficiency across the domains. Once I stopped thinking about a passing "score" and just focused on whether I could reason through realistic situations, something clicked. Passed on the second try with proficient or above across the board.
This is actually really helpful to know — I've been stressing myself out trying to hit some imaginary 75% threshold on practice tests. Still in the thick of studying and honestly the Lean/Agile hybrid stuff is where I keep stumbling. Like I get Scrum and I get Kanban separately, but some of the DA-specific layer on top of that (especially around team-of-teams orchestration) feels like it was written in a different language. Does anyone know if that complexity tends to show up heavily on the actual exam, or is it more surface-level "recognize the term" kind of questions?
Also wondering how much the situational questions lean on context clues vs. actually requiring you to know the DA taxonomy cold. I've been burning a lot of time memorizing the Disciplined Agile Browser categories but if the exam is more about applying judgment in a scenario, I might be studying the wrong way.
This is exactly how I approached it and honestly it changed everything for me. Instead of just drilling questions and trying to memorize which answer is "right," I started asking myself why the other three were wrong. Like really sitting with each distractor and figuring out what concept it was testing incorrectly. It's slower at first but your retention is way better because you're actually building understanding, not just pattern matching. I noticed this especially when I was doing the da security architecture network defense questions — the wrong answers weren't random, they were strategically placed to catch people who half-understood the material.
The scaling thing PMI does actually makes more sense once you think about it this way. If they published a fixed cutoff, people would just aim for that number. By understanding the material deeply enough that you can explain why wrong answers are wrong, you're probably sitting comfortably above whatever the scaled cut is. I didn't stress the exact score target. I just kept practicing until I couldn't be fooled by the distractors anymore, and that felt like a better signal than any percentage ever did.
Honestly I was ready to throw in the towel around week six. I kept second-guessing whether my practice scores were "good enough" and the whole no-fixed-percentage thing made it so hard to know where I stood. What finally clicked for me was focusing on the weak spots instead of chasing an arbitrary number. I drilled into stuff like the da security architecture network defense material because that's where I kept dropping points, and once I stopped worrying about the score and just fixed the gaps, everything shifted.
You don't need a perfect run on every topic. You need to be consistently competent across all of them. I passed on my first attempt and I wasn't acing my practice tests — I was just no longer bombing whole sections. So if you're in that spiral of "is this good enough," just trust the process and address what's actually tripping you up.
Related Discussions
- ICP vs alternatives — which certification is actually recognized more?8 replies
- What CST score do you need to pass? Breaking down the numbers8 replies
- How close are AAC practice tests to the real exam? My honest review7 replies
- Got my PSPO last month — here's what actually changed at work (and what didn't)7 replies
- How much does CAPM actually matter to employers right now?7 replies