Foundation is the paper that asks whether you know AgilePM. Practitioner asks whether you can use it. Neither is harder than the other, but they fail people for completely different reasons, and preparing for one as though it were the other is the most common mistake there is.
What the Foundation Paper Is
Fifty multiple-choice questions in forty minutes. Closed book. A pass mark of fifty percent, twenty-five out of fifty. It is the entry-level AgilePM qualification, and you need it before you can sit Practitioner.
Forty minutes for fifty questions is forty-eight seconds each. That single number shapes everything about how you should prepare. There is no time to reason your way to an answer from first principles, and no handbook to reach for. Either you know it or you are guessing.
The scope is the AgilePM3 v2 Handbook and nothing else: the eight principles, the roles and responsibilities, the artifacts, the lifecycle and its phases, and the core practices including MoSCoW prioritisation, timeboxing, facilitated workshops, modelling and iterative development. Version 3 brings Scrum in as the delivery framework, so the Scrum accountabilities, events and artifacts are in scope alongside the AgilePM project artifacts.
Our free AgilePM3 Foundation practice papers follow that format exactly. The questions do not change between sittings, so you can shuffle their order before you start and a whole room can sit the same paper.
What "Closed Book" Actually Costs You
People underestimate this. Practitioner is open book, and most of the advice floating about online is written with Practitioner in mind: build an index, learn where things are, work out how to find the answer quickly.
None of that helps here. Foundation does not reward navigation. It rewards recall, and recall at speed.
Which means the preparation is different in kind. For Practitioner you rehearse judgement. For Foundation you rehearse retrieval: the eight principles in order, which role is accountable for what, which artifacts belong to which phase, what MoSCoW actually stands for. Dull, and there is no way round it.
The good news is that this is the easier of the two to prepare for, because the material is finite and the questions are fair. Nothing is hidden. Nothing depends on reading a scenario correctly. You are being asked whether you learned it.
The Mistakes People Make in the Real Exam
Five recur.
They prepare by reading rather than by testing. Reading the handbook feels like progress and produces almost no retrieval strength. Sitting a practice paper feels worse and works better, which is why almost nobody does enough of it.
They learn the principles as a list of eight titles. The questions do not ask you to recite them. They describe a situation and ask which principle it illustrates, which requires knowing what each one means, not just what it is called.
They confuse roles across the two frameworks. Version 3 puts Scrum alongside AgilePM, and the overlap is where people lose marks. The Project Manager and the Scrum Master are not the same accountability. The Business Visionary and the Product Owner are not interchangeable. Learn both sets properly and learn where they meet.
They run out of time. Forty-eight seconds a question sounds ample until question thirty-one is one you are unsure of and you spend three minutes on it. Answer it, flag it, move on. An unanswered question scores nothing; a guess scores something.
They treat fifty percent as a low bar. It is twenty-five correct answers out of fifty, with no negative marking and no partial credit. People who are comfortable on the practice papers pass. People who have read the handbook twice and sat nothing often do not.
One Worked Question
Here is the reasoning spelled out, on a question in the exam's style.
During planning, the team agrees that a reporting feature is valuable but that the release would still be usable without it. How should it be prioritised under MoSCoW?
- A. Must have, because the business has asked for it.
- B. Should have, because it is important but the release works without it.
- C. Could have, because it is not essential.
- D. Won't have this time, because it can wait.
Answer: B.
The reasoning. MoSCoW is not a ranking of how much people want things. It is a statement about what the release must contain to be viable at all.
A Must have is not negotiable: without it the release has no value and should not ship. The question says the release would still be usable, which rules A out immediately, however keenly the feature was requested. That distinction is the whole point of the technique and it is where most marks are lost.
The real work is separating B from C. A Should have is important and painful to leave out, but there is a workround. A Could have is genuinely nice to have, and it is the main contingency: the thing dropped first when a timebox gets tight. "Valuable, and the release still works without it" is the textbook description of a Should have.
D is wrong for a different reason worth knowing. "Won't have this time" is a decision, not a holding pen. It means the team has agreed the item is out of scope for this release, which is not what the question describes.
The lesson. Foundation questions are rarely about whether you have heard of a technique. They are about whether you know the line between two of its categories. When a question offers you two plausible neighbours, the answer is almost always in the definition rather than in your instinct.
AgilePM is delivered by Altogether Agile, an accredited practice. The AgilePM qualification is governed by the Agile Business Consortium, the professional body for Business Agility, and accredited by APMG International. Exam formats can change, so confirm the current specification before you book.