Sign in
Home/PRINCE2/PRINCE2 Agile Foundation/Free questions

PRINCE2 Agile Foundation — Free Practice Questions

10 free sample questions from a bank of 52, with the correct answers and explanations. No signup required — start practising right now.

1Whose interests are specifically represented by the senior supplier? 1. Those ensuring the project is value for money. 2. Those who will use the project's products. 3. Those who will be developing the project's products. 4. Those responsible for the project's technical integrity.
  • 1 and 2
  • 2 and 3
  • 3 and 4
  • 1 and 4
Answer: B

The short version

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.

Key concepts in this question

  • Senior supplier: represents those designing, developing, facilitating, procuring and implementing the products.
  • Technical integrity: the senior supplier is accountable for product quality and the integrity of the solution.
  • Board balance: executive owns the business case, senior user owns usage and benefits, senior supplier owns delivery feasibility.

Why 3 and 4 is correct

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.

Why the others are wrong

  • 1. Ensuring value for money is the executive's business-case accountability, not the supplier's.
  • 2. Those who will use the products are the senior user's constituency, representing benefits and fitness for purpose.

PRINCE2-Agile-Foundation exam tip

Board triad in one breath: executive = money, senior user = use, senior supplier = build it right.

2Which BEST describes the senior user role when tailoring the organization theme?
  • An 'agile sponsor'
  • An 'executive sponsor'
  • A 'coach'
  • A 'super product owner'
Answer: D

Verdict: D - a 'super product owner'.

The short version

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.

Key concepts

  • Senior user - the board member who represents the users and the benefits they expect.
  • Super product owner - the agile-tailored name for that board-level product ownership.
  • Agile sponsor / executive sponsor - the senior responsible and the senior responsible's sponsor, both above the project.
  • Coach - a team-level enabler of agile practice, not a board role.

Why D are correct

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.

Why the others are wrong

  • A. An 'agile sponsor' - the sponsor covers funding, strategy and unblocking the project. That is the senior responsible's job; the senior user speaks for users and benefits, not for investment decisions.
  • B. An 'executive sponsor' - that is the sponsor of the senior responsible, sitting above the project board entirely, so it cannot be a board role being tailored.
  • C. A 'coach' - a coach supports the delivery team in adopting agile ways of working. That is team-level enabling, not representation of user interests.

PRINCE2-Agile-Foundation exam tip

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.

3What term is used to describe boards that display what work needs to be completed for people working on a project?
  • Work in progress limit
  • Information radiator
  • Highlight report
  • Glad! Sad! Mad!
Answer: B

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.

4Which two statements about tailoring the business case in an agile environment are CORRECT? 1. It should be unnecessary because products of the highest value will be delivered first. 2. It should identify the minimum viable product and when it will be delivered. 3. It should take into account that the scope may be reduced during the course of the project. 4. It should show the features, the order in which they will be delivered and any dependencies.
  • 1 and 2
  • 2 and 3
  • 3 and 4
  • 1 and 4
Answer: B

Verdict: B - statements 2 and 3.

The short version

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.

Key concepts

  • Business case theme: purpose is to judge whether the project remains desirable, viable and

achievable as a basis for continued investment.

  • Minimum viable product (MVP): the first usable, valuable slice of the product; the agile

equivalent of the traditional benefit/cost profile.

  • Fix and flex (the hexagon): in agile, time and cost are fixed, quality is protected, scope

flexes, and benefits and risk may be fixed or flexed by agreement.

  • Tailoring: PRINCE2 is never used unchanged; the business case is written to flex with the

product.

Why B are correct

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.

Why the others are wrong

  • A. 1 and 2 - statement 1 is false, so this pair fails however right statement 2 is. The

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.

  • C. 3 and 4 - statement 3 is right but statement 4 is release-plan content. The features,

their delivery order and their dependencies belong to the release plan / product-based

planning and the product description, not to the business case.

  • D. 1 and 4 - contains the same false statement 1, and again misplaces statement 4. This

is the unanimous community answer and it is wrong on both of its statements.

PRINCE2-Agile-Foundation exam tip

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.

5What should the business case state about the minimum viable product (MVP)?
  • When the MVP will be defined
  • That the MVP must go into operational use
  • What the MVP is
  • That the MVP is the same as project viability
Answer: C

Verdict: C - what the MVP is.

The short version

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.

Key concepts

  • Business case - mandatory under every PRINCE2 process, and tailored rather than abandoned in agile.
  • Minimum viable product - the first usable, valuable slice of the product.
  • Tailoring guidance - the business case should state what the MVP is and may indicate when it will be delivered.
  • Tolerance - set around the MVP so a forecast to deliver it late, or not at all, is an exception.

Why C are correct

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.

Why the others are wrong

  • A. When the MVP will be defined - the manual says the business case may indicate when it will be delivered, so timing is optional extra. The compulsory content is the definition itself, and that should/may distinction is exactly what the item tests.
  • B. That the MVP must go into operational use - whether the MVP is used operationally is a matter for the customer and the release plan. Mandating it would also collide with the target 'accept that the customer does not need everything'.
  • D. That the MVP is the same as project viability - viability is the business case theme's judgement of whether the investment should continue; the MVP is a product scope concept. Equating them confuses two different ideas.

PRINCE2-Agile-Foundation exam tip

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.

6Which statement about the 'keep teams stable' target is CORRECT?
  • It applies primarily to the long term, such as a project or a program
  • It is the primary reason why the tolerance for cost is set to zero
  • It prevents compromising the overall quality level of the product
  • It results in the early delivery of a minimum viable product
Answer: B

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.

7What needs to happen when new detailed requirements are added to a timebox?
  • Requirements of a similar level of effort should be removed
  • More people should be added to the delivery team
  • The delivery milestones should be reviewed and re-planned
  • Formal change control should be applied
Answer: A

Verdict: A - requirements of a similar level of effort should be removed.

The short version

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.

Key concepts

  • Timebox - a fixed period; in PRINCE2 Agile time and cost are fixed while scope flexes.
  • Negative selection - take work out of equal effort to put work in.
  • Detailed requirements - owned by the delivery level; formal change control applies only to changes to baselined products.
  • MoSCoW / prioritisation - decides what stays in when the timebox cannot grow.

Why A are correct

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.

Why the others are wrong

  • B. More people should be added to the delivery team - adding people mid-timebox attacks the 'keep teams stable' target and the fixed cost tolerance, and new members work at a lower rate initially, so quality would suffer as well.
  • C. The delivery milestones should be reviewed and re-planned - milestones inside a timebox are not the flex. Re-planning is for releases and stages, not for absorbing a single new user story.
  • D. Formal change control should be applied - formal change control in PRINCE2 Agile covers changes to baselined products. Changes to user stories and detailed requirements are handled informally by the team.

PRINCE2-Agile-Foundation exam tip

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.

8Which statement about the 'accept that the customer doesn't need everything' target is correct?
  • It gives confidence on the progress of the project
  • It can result in the early delivery of a minimum viable product
  • It allows misunderstandings to be dealt with appropriately
  • It is achieved by managing the culture of the team carefully
Answer: B

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.

9Which statement about velocity is CORRECT?
  • It is based on the concept of rationalism
  • It is shown by the ideal line on a bum-down chart
  • It describes how much work is getting done
  • It tracks the time and cost of a timebox
Answer: C

Verdict: C - it describes how much work is getting done.

The short version

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.

Key concepts

  • Velocity: rate of progress, used to forecast future delivery empirically on the assumption

that conditions stay the same.

  • Burn chart / burn-down: a progress technique showing work completed and work outstanding,

updated regularly (often daily), usually against a timebox.

  • Ideal line: the planned trajectory on a burn chart - what should have been achieved, not what

was achieved.

  • Rationalism vs empiricism: agile replaces predictive planning with inspect-and-adapt; velocity

exists because outcomes are discovered, not forecast.

Why C are correct

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.

Why the others are wrong

  • A. Based on rationalism - exactly backwards. Rational planning sets a target and defends

it; velocity is an empirical observation used to revise the forecast. Agile explicitly works

on empiricism, so velocity cannot be rationalist.

  • B. Shown by the ideal line on a burn-down chart - the ideal (planned) line is an estimate

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.)

  • D. Tracks the time and cost of a timebox - that describes the timebox and its tolerances,

not velocity. Time and cost are fixed in agile precisely because the scope flexes.

PRINCE2-Agile-Foundation exam tip

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.

10Which is a purpose of the 'controlling stage' process?
  • To execute and deliver the project product
  • To establish whether the project is complete
  • To report stage progress to the project board
  • To draft the plan for the next stage's work
Answer: C

Verdict: C - to report stage progress to the project board.

The short version

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.

Key concepts

  • Controlling a stage - assign work to be done, monitor it, deal with issues, report progress, act to keep the stage within tolerance.
  • Managing product delivery - the team delivers the work packages under the team manager.
  • Managing a stage boundary - review the finished stage, prepare and authorise the next one.
  • Closing a project - accept handover and close, a project-level bookend.

Why C are correct

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.

Why the others are wrong

  • A. To execute and deliver the project product - that is managing product delivery, done by the delivery team. Controlling a stage monitors and steers; it does not do the delivering.
  • B. To establish whether the project is complete - that is closing a project. Stage completeness is judged at a stage boundary, not while the stage is being controlled.
  • D. To draft the plan for the next stage's work - that is managing a stage boundary, which happens near the end of the current stage.

PRINCE2-Agile-Foundation exam tip

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.