Question 1

Agilometer

Accepted Answer

A tool used in PRINCE2 Agile to measure the level of agility suitable for a particular project.

Question 2

Agnostic

Accepted Answer

This term in PRINCE2 Agile refers to the framework's ability to work with any Agile delivery method.

Question 3

Batching

Accepted Answer

The process of grouping together similar items or tasks to be worked on at the same time.

Question 4

Blending

Accepted Answer

The concept of combining elements of PRINCE2 and Agile practices to deliver projects efficiently.

Question 5

Burn-up Chart

Accepted Answer

A graphical representation showing the amount of work completed over time.

Question 6

Burn-down Chart

Accepted Answer

A graphical representation showing the amount of work remaining over time.

Question 7

Collabortive Communication

Accepted Answer

A type of communication emphasized in PRINCE2 Agile that fosters team collaboration and problem solving.

Question 8

Concession

Accepted Answer

The recognition of a product defect but deciding to do nothing about it for now.

Question 9

Configuration Item Record

Accepted Answer

A document that records the life of a product.

Question 10

Contingency

Accepted Answer

A plan or preparation for potential problems or risks.

Question 11

Cynefin

Accepted Answer

A decision-making framework used to determine the complexity of a given situation and respond accordingly.

Question 12

Daily Stand-up

Accepted Answer

A regular, brief meeting where team members update each other on their progress.

Question 13

Deliver on Time

Accepted Answer

An Agile principle that emphasizes the importance of meeting deadlines.

Question 14

Disaggregation

Accepted Answer

The breaking down of complex tasks or products into simpler, manageable chunks.

Question 15

Epic

Accepted Answer

A large user story that can be broken down into smaller user stories.

Question 16

Exploratory Testing

Accepted Answer

An approach to testing that emphasizes personal freedom and responsibility of the individual tester.

Question 17

Flex

Accepted Answer

The ability to adjust what is delivered and when, without changing the project's overall scope.

Question 18

Flow

Accepted Answer

The smooth, uninterrupted movement of work within a team or process.

Question 19

Frequent Releases

Accepted Answer

An Agile principle that emphasizes delivering value to the customer regularly and often.

Question 20

Health Check

Accepted Answer

A review process to assess the health of an Agile project.

Question 21

Hindsight

Accepted Answer

The examination and understanding of past actions and decisions.

Question 22

Horizon Scanning

Accepted Answer

The act of looking ahead to identify future risks and opportunities.

Question 23

Increment

Accepted Answer

A portion of the product that is considered complete and can be delivered to the customer.

Question 24

Information Radiator

Accepted Answer

A large, highly visible display used to show team progress and performance.

Question 25

Iteration

Accepted Answer

A complete development loop resulting in a release of an increment of the product, potentially shippable.

Question 26

Kanban

Accepted Answer

A visual system for managing work as it moves through a process.

Question 27

Kaizen

Accepted Answer

A Japanese word meaning 'improvement', often used in the context of continuous improvement.

Question 28

Lean

Accepted Answer

An Agile methodology that emphasizes reducing waste and improving efficiency.

Question 29

MoSCoW

Accepted Answer

A prioritization technique used in management, business analysis, project management, and software development to reach a common understanding with stakeholders.

Question 30

Non-functional Requirement

Accepted Answer

A requirement that specifies the system’s operation, performance, and quality.

Question 31

Off-specification

Accepted Answer

A product that should be provided by the project but currently is not or is forecast not to be.

Question 32

Outcomes, Outputs, Benefits

Accepted Answer

The hierarchy of project objectives in PRINCE2.

Question 33

Product Description

Accepted Answer

A document that provides a detailed description of a product's purpose, composition, derivation, and quality criteria.

Question 34

Product Backlog

Accepted Answer

An ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.

Question 35

Product Owner

Accepted Answer

A role in Scrum responsible for defining and prioritizing the product backlog and ensuring the team is working on the most valuable features.

Question 36

Progress

Accepted Answer

One of the seven PRINCE2 themes that deals with the ongoing viability of the plans.

Question 37

Project Assurance

Accepted Answer

The PRINCE2 role responsible for monitoring the project's performance and ensuring it aligns with the project's objectives.

Question 38

Project Product Description

Accepted Answer

A special type of product description defining what the project must deliver in order to gain acceptance.

Question 39

Quality

Accepted Answer

One of the seven PRINCE2 themes that helps determine whether the project's products are fit for purpose.

Question 40

Quality Criteria

Accepted Answer

A description of the attributes required for a set of products to be fit for purpose.

Question 41

Quality Review

Accepted Answer

A structured method for reviewing the quality of a product.

Question 42

Quality Review Technique

Accepted Answer

A technique used to assess a product's quality by gathering experts and stakeholders for a structured discussion.

Question 43

RACI (Responsible, Accountable, Consulted, Informed)

Accepted Answer

A matrix used to clarify roles and responsibilities in cross-functional or departmental projects and processes.

Question 44

RAD (Rapid Application Development)

Accepted Answer

An adaptive software development approach that prioritizes rapid prototype releases and iterations.

Question 45

Refined User Stories

Accepted Answer

User stories that are ready to be estimated and planned for an upcoming iteration.

Question 46

Retrospective

Accepted Answer

A meeting held at the end of an iteration to discuss what was successful and what could be improved.

Question 47

Risk

Accepted Answer

One of the seven PRINCE2 themes that deals with identifying, assessing, and controlling uncertainty.

Question 48

Scrum

Accepted Answer

An Agile framework that encourages teams to work adaptively and iteratively towards a goal.

Question 49

Scrum Master

Accepted Answer

A role in Scrum responsible for promoting and supporting the Scrum framework within the team.

Question 50

Scrum of Scrums

Accepted Answer

A technique used to scale Scrum up to large groups, where multiple Scrum teams synchronize their work.

Question 51

Self-organizing Teams

Accepted Answer

Teams that decide internally how to best accomplish their work, rather than being directed by others outside the team.

Question 52

Servant Leadership

Accepted Answer

A leadership philosophy where the main goal of the leader is to serve, emphasized in Scrum and other Agile methods.

Question 53

Sprint

Accepted Answer

A time-boxed iteration of product development in Scrum.

Question 54

Sprint Backlog

Accepted Answer

A list of tasks identified by the Scrum team to be completed during the Scrum sprint.

Question 55

Sprint Review

Accepted Answer

A meeting at the end of each sprint where the team inspects what they delivered and adapt the product backlog if needed.

Question 56

Sprint Retrospective

Accepted Answer

A meeting held at the end of each sprint where the Scrum team inspects itself and creates a plan for improvements to be enacted during the next sprint.

Question 57

Sprint Zero

Accepted Answer

The period of time before the first sprint, used for planning and preparation.

Question 58

Stakeholder

Accepted Answer

Any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project.

Question 59

Stand-up

Accepted Answer

A daily meeting in Agile methodologies used to ensure open communication among team members.

Question 60

Timeboxing

Accepted Answer

A technique that limits the amount of time spent on an activity.

Question 61

Tolerance

Accepted Answer

The permissible deviation from the plan before corrective action is needed.

Question 62

Use Case

Accepted Answer

A list of actions or event steps defining the interactions between a role and a system.

Question 63

Velocity

Accepted Answer

A metric that predicts how much work an Agile team can successfully complete within an iteration or a sprint.

Question 64

Version Control

Accepted Answer

A system that records changes to a file or set of files over time so that you can recall specific versions later.

PRINCE2 Agile Practitioner