PRINCE2-Agile-Foundation Exam Practice Test Instant Access

Question 1

Which of the following describes shared attitudes, values, and goals?

ACulture

BLeadership

CCo-creation

DManagement

Answer : A

Culture refers to the collective attitudes, values, beliefs, and goals shared by a group or organization. It shapes how people behave, make decisions, and interact. In PRINCE2 Agile, understanding and adapting organizational culture is critical for successful agile adoption and delivery.

Leadership (B) influences culture but is distinct, co-creation (C) is a collaborative approach, and management (D) relates to planning and control activities.

A positive, agile-friendly culture fosters openness, trust, and continuous improvement.

Question 2

Which artifact is used to describe the project's major products in the form of epic user stories?

AProject dashboard

BRelease map

CProduct backlog

DProject backlog

Answer : D

The Project Backlog is the artifact used to describe the project's major products in the form of epic user stories. Epic stories are large, high-level user stories that capture significant features or product components that may later be decomposed into smaller, more detailed user stories in the product backlog.

The Project Backlog provides a strategic view of what the project intends to deliver and supports planning at the project level, including releases and stages. It bridges the gap between business requirements and team-level delivery.

The Product Backlog (C) contains detailed user stories ready for development but is typically more granular. The Release Map (B) plans releases and iterations but does not list epic stories. The Project Dashboard (A) is a reporting tool, not a repository of requirements.

The use of epic user stories in the project backlog aligns with agile practices for managing scope and enables incremental delivery aligned with business priorities.

Question 3

How are user inputs FIRST gathered in the 'quality' practice?

AAs user stories in the product backlog

BAs epic user stories in the project backlog

CAs the project Definition of Done in the quality management approach

DAs a quality control activity in the quality register

Answer : A

User inputs are initially gathered as user stories in the product backlog in PRINCE2 Agile. User stories represent small, customer-focused requirements that capture the 'who,' 'what,' and 'why' of a feature. These stories form the foundation of requirements and quality criteria for the product and ensure that development is driven by user needs and value delivery.

The Definition of Done is developed later as part of the quality management approach to specify when work is complete. Epic user stories are larger features that can be broken down into smaller user stories. The quality register tracks quality-related activities but is not the first step for gathering user inputs.

Question 4

Which statement about the 'accept that the customer doesn't need everything' target is CORRECT?

AIt is achieved by testing only a few features to deliver on time

BIt is achieved by ensuring that the operational product has complete documentation

CIt is based on the concept that people generally use a limited number of product features

DIt enables a more accurate final product to be produced

Answer : C

Question 5

Which statement about velocity is CORRECT?

AIt is based on the concept of rationalism

BIt is shown by the ideal line on a bum-down chart

CIt describes how much work is getting done

DIt tracks the time and cost of a timebox

Answer : C

Question 6

How should product-based planning be used as part of PRINCE2 Agile?

ATo track progress against the team plan

BTo create the project plan using empiricism

CTo enable team planning to be predictive

DTo plan by focusing on the features required

Answer : D

Question 7

What is the purpose of the 'progress' practice?

ATo provide a forecast for the project's viability

BTo identify and assess opportunities and threats

CTo identify the user needs and requirements

DTo establish accountability for the project

Answer : A

The Progress practice in PRINCE2 Agile is focused on providing a forecast of the project's viability by monitoring actual progress against plans and predicting future performance. It ensures that decisions can be made based on current status and trends, enabling timely interventions if necessary.

This practice involves collecting progress data, reviewing milestones, updating forecasts, and communicating status to stakeholders. Forecasting viability includes assessing whether the project remains aligned with business justification and expected benefits.

While opportunities and threats are part of risk management (B), user needs belong to requirements management (C), and accountability is a broader governance concern (D), progress specifically deals with tracking and forecasting delivery status.

The practice combines traditional PRINCE2 stage controls with agile iterative reviews, providing an integrated view of progress.

PRINCE2 Agile Foundation PRINCE2-Agile-Foundation Exam Practice Test