10 free sample questions from a bank of 52, with the correct answers and explanations. No signup required — start practising right now.
3 and 4 — the senior supplier speaks for the builders and for technical integrity. Value for money belongs to the executive and product use belongs to the senior user.
Statement 3 (those developing the products) is the textbook definition of the supplier interest: the in-house or external teams providing the skills and resources that design and build the outputs. Statement 4 (those responsible for technical integrity) is the senior supplier's explicit accountability — quality of the delivered products and integrity of the solution, including judging whether design and development proposals are realistic. The settled answer pairs them, and the community agrees unanimously.
Board triad in one breath: executive = money, senior user = use, senior supplier = build it right.
Verdict: D - a 'super product owner'.
In an agile context the senior user role is tailored into a super product owner: the board-level person who owns the product vision and steers the delivery team's product owner. The other three labels belong to other roles - the two kinds of sponsor and the team coach.
The senior user's interest is the user: what people need from the product and the benefits they expect. In an agile context that interest is exercised as product ownership. Keeping the vision with the board while the team's product owner orders the work is exactly the agile-tailored shape of the role, and 'super product owner' names it.
When a question asks how a PRINCE2 role changes in agile, ask what that role cares about. The senior user's care is the user's needs and the benefits, so in agile the role becomes product ownership at board level. Sponsors fund; coaches enable; only the super product owner carries user value into delivery.
B is correct: an information radiator is the visible board or display where a team keeps its product goal, release plan, progress, risks and issues, so anyone can pull the information instead of asking. A work in progress limit caps how much work is in progress, C a highlight report is a summary for management, and D Glad! Sad! Mad! is a stakeholder mood technique.
Verdict: B - statements 2 and 3.
The business case is mandatory in PRINCE2, even in an agile project, so it is tailored rather
than dropped. The agile-tailored business case must say what the minimum viable product (MVP)
is and roughly when it lands, and must be written on the assumption that scope will move. That
is exactly statements 2 and 3.
achievable as a basis for continued investment.
equivalent of the traditional benefit/cost profile.
flexes, and benefits and risk may be fixed or flexed by agreement.
product.
Statement 2 (identify the MVP and when it will be delivered) is the manual's explicit
requirement - the business case "should clearly state what the minimum viable product is and
may give an indication of when this will be delivered", with tolerances set around it so a
late or absent MVP raises an exception. Statement 3 (allow for the scope being reduced during
the project) is the second half of tailoring the business case for agility: in PRINCE2 Agile it
has to be flexible and "written on the assumption that what is being delivered will change",
because scope is the flexed performance target.
business case is a mandatory management product under every PRINCE2 process; delivering the
highest-value items first does not remove the need to justify the investment.
their delivery order and their dependencies belong to the release plan / product-based
planning and the product description, not to the business case.
is the unanimous community answer and it is wrong on both of its statements.
Learn the boundary between the four management products: the business case justifies and
quantifies the investment (benefits, costs, risks, MVP); the release plan and product-based
plan sequence the features and their dependencies. In a two-statement question, first eliminate
any option built on "the business case is unnecessary" - that is never true in PRINCE2.
Verdict: C - what the MVP is.
The business case must state what the minimum viable product is. It may then indicate when it will be delivered, and tolerances are set around that statement so a late or missing MVP raises an exception. Timing, operational use and viability are not what it has to state.
In agile the business case has to give the board something concrete to judge, and the MVP is that something: the first release of real value. Because the investment case is then anchored to a defined deliverable, tolerances can be set around it and a late or absent MVP escalates. What it must state is the definition of the MVP; when it lands is optional extra information.
Watch the modal verbs in the manual: the business case should state what the MVP is and may indicate when it will be delivered. Items that make the timing compulsory, mandate operational use, or equate the MVP with viability are on the wrong side of that line.
B is correct: keeping teams stable means the cost of the project cannot be recovered by adding people part way through, which is why PRINCE2 Agile sets the cost tolerance to zero - fixed, not flexed. C and D are benefits of protecting quality and of accepting that the customer does not need everything, and A describes the long-term level of governance, not this target.
Verdict: A - requirements of a similar level of effort should be removed.
Detailed requirements inside a timebox belong to the delivery level, so when new ones arrive the team removes work of comparable size to make room. Time is fixed and cost is fixed, so the backlog content is the only thing that can move.
A timebox cannot be enlarged, the team cannot be enlarged (keep teams stable, zero cost tolerance) and quality cannot be traded away. So the content has to absorb the change: the new detailed requirements come in and an equivalent amount of effort goes out. That swap is negative selection, and it is how the team keeps control without change control.
Fixed timebox plus fixed cost plus protected quality means scope is the only variable, so the answer to 'what happens when new detailed requirements arrive' is always negative selection: work of similar size comes out.
B is correct: the customer agrees the product need not be complete, so a usable minimum viable product can be delivered early and its feedback steers everything built after it. A and C describe the confidence and progress targets, and D is about the culture of a self-managing team, not this target.
Verdict: C - it describes how much work is getting done.
Velocity is a simple measure of throughput: how much work the team actually completed in an
iteration (for example 20 user stories a sprint). It is an empirical, historical measure, not a
prediction - and that is the whole point of it.
that conditions stay the same.
updated regularly (often daily), usually against a timebox.
was achieved.
exists because outcomes are discovered, not forecast.
Velocity "describes how much work is getting done". It is a retrospective count of completed
work per iteration, which lets the team forecast empirically - "if a team is completing 20 user
stories per week then this is their velocity and it can be used to empirically forecast their
future rate of progress". It is never a percentage, a date or a cost figure.
it; velocity is an empirical observation used to revise the forecast. Agile explicitly works
on empiricism, so velocity cannot be rationalist.
drawn before the work; velocity is the actual achieved rate. Reading velocity off the ideal
line would defeat the purpose of an empirical measure. (This is the unanimous community pick
and it confuses the plan with the measurement.)
not velocity. Time and cost are fixed in agile precisely because the scope flexes.
Memorise the pairing: burn charts show progress, and velocity is the actual rate of progress
(the real line), never the ideal line. Anything that describes a target, a percentage or a
budget is a distractor.
Verdict: C - to report stage progress to the project board.
Controlling a stage is the project manager monitoring the work assigned inside the stage, dealing with issues, taking corrective action to stay within tolerance, and reporting progress up to the board. Delivering the product, closing the stage and planning the next one are other processes.
The purpose of controlling a stage is to keep the stage on track inside its tolerances and to give the board what it needs to direct the project. Monitoring delivery, managing issues and reporting progress up are exactly that; the project manager never leaves the stage to go and close it or plan the next one.
Match the verb to the process: assign/monitor/report = controlling a stage; accept/execute/evaluate work packages = managing product delivery; review/prepare next/authorise = managing a stage boundary; accept handover and close = closing a project.
Want the full bank of 52 questions for PRINCE2 Agile Foundation? See all practice exams.