HomePRINCE2 Agile Practitioner NewQuestions 21–30
PRINCE2 Agile PractitionerPart 3 of 3

PRINCE2 Agile Practitioner Exam Questions & Answers 2026 (21–30)

PRINCE2 Agile Practitioner practice questions and answers 2026. Tap an option to test yourself — you'll see the correct answer and a plain-English explanation for every question. Free, no login.

Practise PRINCE2 Agile Practitioner questions free, download the PDF, or unlock timed mock exams when you are ready.
Download PDFWatch video
Multiple choice — pick the best answer, then reveal it
  1. Q21Which framework structures work into fixed-length, time-boxed iterations?

    • AScrum
    • BKanban
    • CLean
    • DWaterfall
    • EPrince2
    Show answer

    ✓ Correct answer: A. Scrum

    Scrum organises work into fixed-duration sprints, making it inherently time-boxed. Why the other options are incorrect: • Kanban: Kanban operates on a continuous flow basis without fixed iterations. • Lean: Lean focuses on eliminating waste rather than time-boxing work. • Waterfall: Waterfall follows a linear, sequential progression through stages. • Prince2: PRINCE2 is a project management governance framework.

  2. Q22What characteristic best describes a typical agile workshop?

    • AFull engagement from all participants
    • BInformation flowing in only one direction
    • CProduction of lengthy written reports
    • DInstructions handed down from leadership
    • EFixed decisions about project scope
    Show answer

    ✓ Correct answer: A. Full engagement from all participants

    Agile workshops depend on every attendee actively engaging throughout the session. Why the other options are incorrect: • Information flowing in only one direction: Workshops involve two-way, open dialogue rather than one-way delivery. • Production of lengthy written reports: Workshops minimise heavy documentation rather than producing it. • Instructions handed down from leadership: Top-down directives undermine the collaborative nature of workshops. • Fixed decisions about project scope: Scope is treated as flexible and iteratively refined, not locked down.

  3. Q23Which aspect of Kanban prevents teams from taking on too many tasks at once?

    • ACaps on work in progress
    • BComprehensive upfront design
    • CHeavy documentation requirements
    • DInflexible milestone schedules
    • ECommand-and-control management
    Show answer

    ✓ Correct answer: A. Caps on work in progress

    WIP limits reduce overload and help maintain a steady, sustainable flow of work. Why the other options are incorrect: • Comprehensive upfront design: Heavy upfront design conflicts with agile and Kanban thinking. • Heavy documentation requirements: Kanban favours minimal, just-enough documentation. • Inflexible milestone schedules: Kanban treats milestones as adaptable, not fixed. • Command-and-control management: Kanban promotes shared, collaborative leadership rather than command-driven control.

  4. Q24Which of the following is an example of a business as usual outcome?

    • AUpgrading a system
    • BConstructing new offices
    • COngoing customer support
    • DLaunching a new product
    • EEnd-of-project summary
    Show answer

    ✓ Correct answer: C. Ongoing customer support

    Providing ongoing customer support is a repeating operational activity, making it an example of business as usual. Why the other options are incorrect: • Upgrading a system: Upgrading a system involves a defined scope and end point, making it project work. • Constructing new offices: Constructing new offices is a time-limited, one-off undertaking, which is characteristic of a project. • Launching a new product: Launching a new product is a unique, time-bound effort, placing it firmly in the domain of projects. • End-of-project summary: An end-of-project summary is produced at the close of a project, not as part of routine operations.

  5. Q25At which maturity level can agile success be tracked using measurable metrics?

    • AManaged
    • BAwareness
    • CAd hoc
    • DResistant
    • EInitial
    Show answer

    ✓ Correct answer: A. Managed

    The Managed level is where agile outcomes become measurable and can be tracked quantitatively. Why the other options are incorrect: • Awareness: Awareness involves only a basic, early understanding of agile concepts. • Ad hoc: Ad hoc lacks the consistency required for meaningful measurement. • Resistant: Resistance to change prevents maturity from advancing. • Initial: Initial is the stage before agile has been adopted at all.

  6. Q26Which of the following is a defining characteristic of a project?

    • ANo fixed finish
    • BTime-bound
    • CUninterrupted
    • DRepetitive
    • EUnchanged
    Show answer

    ✓ Correct answer: B. Time-bound

    By definition, a project is time-bound and has a finite duration. Why the other options are incorrect: • No fixed finish: Having no fixed finish is characteristic of BAU. • Uninterrupted: Uninterrupted, continuous work describes BAU. • Repetitive: Repetitive tasks are a feature of BAU operations. • Unchanged: Unchanged, stable work is associated with BAU.

  7. Q27Which of the following is more characteristic of business as usual than of a project?

    • ATime-limited aims
    • BSpecified outcomes
    • CStable, repeated procedures
    • DFixed duration
    • EOne-of-a-kind result
    Show answer

    ✓ Correct answer: C. Stable, repeated procedures

    Business as usual is marked by stable, repeated procedures that do not fundamentally change over time. Why the other options are incorrect: • Time-limited aims: Goals with a limited lifespan are associated with projects, not business as usual. • Specified outcomes: Clearly specified outcomes are a feature of projects, not routine operations. • Fixed duration: Having a fixed duration is a characteristic of projects; business as usual continues indefinitely. • One-of-a-kind result: Producing a one-of-a-kind result is what projects do, not business as usual.

  8. Q28During an agile adoption, which activity best limits exposure to transition risk?

    • ARunning a pilot project
    • BDeploying organisation-wide from day one
    • CRemoving all existing governance structures
    • DLocking down the project scope
    • ESkipping staff training
    Show answer

    ✓ Correct answer: A. Running a pilot project

    A pilot project lets a team trial agile practices in a contained setting before broader rollout, limiting overall risk. Why the other options are incorrect: • Deploying organisation-wide from day one: Rolling out across the whole organisation immediately amplifies rather than reduces risk. • Removing all existing governance structures: Governance structures still serve an important purpose and should not be discarded. • Locking down the project scope: One of agile's defining traits is that scope is expected to evolve throughout delivery. • Skipping staff training: Adequate training is a prerequisite for a successful agile adoption.

  9. Q29Which Kanban practice is focused on raising performance over time?

    • AImprove through shared, collaborative effort
    • BRecord every process step in detail
    • CDiscourage experimentation within the team
    • DStop collecting performance data
    • EDismiss incoming feedback
    Show answer

    ✓ Correct answer: A. Improve through shared, collaborative effort

    Collaborative, evolutionary improvement is one of Kanban's six core practices, driving continuous performance gains. Why the other options are incorrect: • Record every process step in detail: Kanban avoids unnecessary documentation overhead. • Discourage experimentation within the team: Running experiments is how teams learn and adapt within a Kanban system. • Stop collecting performance data: Metrics are key to identifying where improvement is possible. • Dismiss incoming feedback: Feedback is central to the continuous improvement cycle in Kanban.

  10. Q30According to agile values, what should take priority over comprehensive documentation?

    • AOver documentation
    • BOver collaboration
    • COver processes
    • DOver contracts
    • EOver testing
    Show answer

    ✓ Correct answer: A. Over documentation

    The Agile Manifesto explicitly states that working software should be valued over extensive documentation. Why the other options are incorrect: • Over collaboration: Collaboration with customers is itself highly prized in agile and is not deprioritised. • Over processes: While processes have a place, agile values outcomes and people over rigid adherence to them. • Over contracts: Agile values customer collaboration over contract negotiation, so contracts are already considered secondary. • Over testing: Testing is an integral part of delivering working software and supports rather than conflicts with it.

Free practice here. Timed mocks when you are ready.

Use the free PRINCE2 Agile Practitioner New sample, download the PDF, then unlock web-based timed mock exams for a full exam rehearsal.

Download PDFStart practice test