-
Acceptance Criteria
-
Measurable definitions of the attributes required for a deliverable to be acceptable to stakeholders.
-
Agile Coach
-
An agile role that serves as a mentor and facilitator helping organizations adopt and sustain agile principles and practices. The agile coach assists with creation of epic user stories and facilitates project workshops and project board workshops. They work across teams and guide leaders in improving collaboration, promoting agile values, and enabling continuous delivery of value.
-
Agile Onion
-
A metaphor coined by Simon Powers, commonly used to depict the layers of agile understanding and implementation, normally represented as a Venn diagram. Each layer represents a different aspect of agile, moving from surface-level practices to deeper values and principles that shape how teams operate.
-
Agile Transformation Plan
-
A plan guiding an initiative to adopt (more) agility. It contains high-level goals aligning new target states to organizational strategy (for example, mission/vision), as well as short-term objectives to guide the practical implementation of these new target states.
-
Agility
-
The ability to embrace and respond to change, by pivoting and adapting a previously set course.
-
Agilometer
-
A tool that assesses the level of risk associated with using agile in the current environment and answers the questions of ‘How agile our environment is?’ and ‘How agile can we be?’. The next step is to see what can be done to improve agility.
-
Backlog
-
A prioritized list of the requirements for a product. The list may be made up of (epic) user stories or other formats of requirements. There are two types of backlogs in PRINCE2 Agile: project backlog and product backlog. The project backlog usually contains high-level requirements in the form of epic user stories and is owned by the CPO. Product backlogs are used at the team level and consist of user stories which the delivery team will be expected to deliver and are owned by the PO(s).
-
Baseline
-
Reference levels against which an entity is monitored and controlled.
-
Baseline Change
-
A modification to any of the approved products that constitute the project baseline.
-
Baseline Management Product
-
A type of management product that defines aspects of the project and, when approved, is subject to change control.
-
Behaviour-Driven Development (BDD)
-
A development process based on TDD. It is usually more collaborative and implements the general techniques and principles of TDD in a wider behavioural context (e.g. what the user may want to achieve). It uses a style of language that users can understand easily (hence the use of words such as “behaviour” in BDD).
-
Benefit
-
The measurable improvement resulting from an outcome that is perceived as an advantage by the investing organization and contributes towards one or more business objectives.
-
Burn Chart
-
A visual representation of progress, where work is mapped against time. There are two types of burn charts. A burn-down chart is a run chart of outstanding work over time. A burn-up chart is a run chart of completed work against a deadline.
-
Business
-
The organization that provides the project mandate and the structure within which the project is governed. Any use of the term ‘business’ within this book specifically refers to this organization.
-
Business Analyst
-
A role that bridges the gap between stakeholders and development teams by gathering, analysing, and documenting requirements. They ensure that solutions align with business needs and add value to the organization.
-
Business Case
-
A management product documenting the business justification for a project, based on the estimated costs against the expected benefits to be gained and offset by any associated risks.
-
Business Layer
-
The layer of governance outside the project team that sets the overall objectives and tolerance levels for the project and holds the project board accountable for meeting them.
-
Business Objective
-
The measurable outcomes that demonstrate progress in relation to the organization’s strategy to which the project should contribute.
-
Capability
-
The completed set of project outputs required to deliver an outcome.
-
Change Authority
-
A person or group to which the project board may delegate responsibility for the consideration of requests for change or off-specifications. The change authority may be given a change budget and can approve changes within that budget.
-
Change Budget
-
The money or authorized constraints set aside in a plan to cover changes. It is allocated by those with delegated authority to deliver authorized changes.
-
Checkpoint Report
-
A report from a team to the project manager outlining the status of the work package at the frequency agreed with the project manager.
-
Chief Product Owner (CPO)
-
A version of the senior user role tailored to the agile context. They represent the user community and are accountable for the approach taken to capture user requirements in the project backlog and for the specification of benefits. The CPO owns the project backlog.
-
Co-Creation
-
A specific form of collaboration involving users and key influencers in the design of products and agreed ways of working to ensure they are adopted throughout the ecosystem.
-
Collaboration
-
People from across the ecosystem working together to achieve the shared objectives.
-
Constraints
-
The restrictions or limitations by which the project is bound.
-
Culture
-
The set of shared attitudes, values, goals, and ways of working that characterize a group of people.
-
Customer
-
Where there is a commercial relationship between the business and the supplier, the business is regarded as the customer (this is typically where the user is external from the business and may pay for the project or the products).
Are you ready to become a certified PRINCE2 Agile professional? Click here to explore relevant certification trainings and achieve the next level in Agile Proejct Management.
-
Daily (Meeting)
-
A 15-minute, daily alignment meeting where a team communicates progress, gathers obstacles (which will be discussed after, not during the daily), and plans work for the next 24 hours. Ideally, it occurs at the same place/time and in front of a dashboard. It is self-managed by the team.
-
Daily Log
-
A log used to record problems/concerns that can be handled by the project manager informally.
-
Dashboard
-
A visual representation that gives a current summary, usually in graphic, easy-to-read form, of key information relating to the progress and performance of the project or team. In PRINCE2 Agile, there are two types of dashboards: project dashboard and team dashboard. The project dashboard displays the current status of the plan and releases, burn charts, current risks and issues, as well as the agile assessment trends. Team dashboards display the team plan, product backlog items, iteration status, burn charts, current risks and issues, team values and agreements.
-
Definition Of Done (DoD)
-
A list of quality criteria to determine if work has been completed in alignment with user acceptance needs. This ensures that all work, usually in the form of user stories, is held to the same overarching quality standards before being deemed ‘done’ for quality reviews.
-
Definition Of Ready (DoR)
-
A list of quality criteria to determine if work can be started on something such as a user story. This is a measure of quality to ensure that only well-defined and understood requirements move on to development and less time is wasted on clearing up misunderstandings.
-
Delivery Method
-
The way in which the work of the project is to be delivered. The project may rely on one or more delivery methods to create the required products. Typical delivery methods include iterative-incremental, linear-sequential, or hybrid.
-
Demo
-
Short for ‘demonstration’, this is an event where a product or interim product, in whatever state of readiness, is shown to a person or group to get feedback and show progress. The product being “demoed” could be static (e.g. a paper design) or dynamic (e.g. a working prototype).
-
Developer
-
A role in the delivery team responsible for developing products, contributing to their design, and collaborating with other team members to ensure technical feasibility. They resolve technical issues and continuously improve the outputs by adhering to agile best practices.
-
DevOps
-
An organizational culture that aims to improve the flow of value to customers. DevOps focuses on culture, automation, Lean, measurement, and sharing (CALMS).
-
Dis-Benefit
-
The measurable decline resulting from an outcome that is perceived as negative by the investing organization and detracts from one or more business objectives.
-
Empiricism
-
Evidence-based approach to planning, estimating, and decision-making often contrasted against a reasoning approach based on intuition.
-
End Project Report
-
A report given by the project manager to the project board, confirming the handover of all products. It includes a review of the performance of the project, any subsequent recommendations, and request approval to close the project.
-
End Stage Report
-
A report given by the project manager to the project board at the end of each stage. This provides information about the project’s performance during the stage and the project status at the stage end.
-
Epic (User Story)
-
A high-level definition of a requirement that has not been sufficiently refined or understood yet. Eventually, an epic will be refined and broken down into several user stories or requirements.
-
Exception
-
A situation where it can be forecast that there will be a deviation beyond the tolerance levels agreed between the project manager and the project board (or between the project board and business layer).
-
Exception Plan
-
A plan that follows an exception report and explains how the project will respond to the exception within the stage.
-
Exception Report
-
A report from the project manager to the project board to explain where tolerances have or are forecast to be breached for the stage or project and to request direction from the project board.
-
Experiment
-
An investigation into something that is carried out in a series of specific steps (which may involve research) to prove or disprove a theory or idea. This can be used to validate an idea or to try to improve something such as the way a team is working.
-
Feature
-
A generic term that is widely used to describe something a product does, or the way in which a product does something. A feature can be at any level of detail (for example, it is waterproof, it makes a tone when switched off) and can be related to a specific requirement, user story, or epic.
-
Flow-Based
-
This approach avoids the use of partitioning work into timeboxes and manages work by using a queue. Work is then continually pulled into the system (which may itself be a high-level timebox) and moves through various work states until it is done.
-
Forecast
-
A prediction made by studying historical data and past patterns.
-
Growth Mindset
-
The core belief that anyone is capable of learning and adapting.
-
Handover
-
The transfer of ownership of a set of products to the respective user(s). The set of products is known as a release. There may be more than one handover during the life of a project (phased delivery).
-
Highlight Report
-
A time-driven report from the project manager to the project board on stage progress.
-
Issue
-
An event relevant to the project that requires project management consideration.
-
Issue Register
-
A register used to capture and maintain information on all issues that are being managed formally. The issue register should be monitored by the project manager on a regular basis.
-
Issue Report
-
A report containing the description, impact assessment, and recommendations for a response to an issue. It is created only for those issues that need to be handled formally.
-
Iteration
-
A specific type of timebox focused on delivering incremental product value. It encompasses planning, development, testing, and review within the set time period.
-
Kanban
-
An approach to improve flow and provoke system improvement through visualization and controlling work in progress. It relies on a “pull system” implemented by limiting the number of work items in circulation to identify possible bottlenecks in processes.
-
Leadership
-
Motivating people to achieve objectives. This is best done through collaboration across the ecosystem, persuading, influencing, and co-creating with a focus on managing key relationships and seeking regular feedback to ensure team members remain aligned to the objectives and agree to joint ways of working.
-
Lean
-
An approach that focuses on improving processes by maximizing value through eliminating waste (such as wasted time and wasted effort).
-
Lean Startup
-
Originally an approach to creating and managing start-up companies, but now applied to any business, to help them deliver products to customers quickly.
-
Lessons Log
-
An informal repository for lessons that apply to this project or future projects.
-
Lessons Report
-
A report used to share lessons and trigger actions to ensure that lessons become embedded in the appropriate organization’s way of working.
-
Management
-
Instructing the execution of tasks in line with agreed ways of working. Co-creating ways of working with team members (and stakeholders) significantly improves people’s willingness to be managed in line with them.
-
Management Approaches
-
The procedures, techniques, and standards to be applied and the responsibilities for: benefits management, change management, commercial management, communication management, data management, issue management, quality management, risk management, and sustainability management.
-
Management Product
-
A product that will be required as part of managing the project and establishing and maintaining quality (for example, highlight report and end stage report). The management products are constant, whatever the type of project, and can be used as described, or with any relevant modifications, for all projects. There are three types of management product: baselines, records, and reports.
-
Metric
-
A measurement or calculation that is monitored or reported for management and improvement.
-
Milestone
-
A significant event in a plan’s schedule, such as completion of key work packages, a development step, or a stage.
-
Minimum Viable Product (MVP)
-
Used in agile development methods to describe a product with just enough features to satisfy early customers who can then provide feedback for future product development. Typically, an MVP would be delivered as early as possible during the project. It is important to note that an MVP is about learning and may not go into operational use; it may be in the form of a simple experiment or prototype.
-
MoSCoW Prioritization
-
A technique used to categorize items such as requirements or tasks based on their level of priority/importance: Must have, Should have, Could have, Won’t have (for now).
-
Objectives And Key Results (OKR)
-
A goal-setting framework that helps organizations define and track ambitious goals. It consists of two main components: objectives which are clear, aspirational business goals that define what the organization wants to achieve, and key results which are specific, measurable outcomes that indicate progress towards achieving the objective.
-
Off-Specification
-
A product that will not meet its quality specifications.
-
Opportunity
-
An uncertain event that could have a positive impact on objectives.
-
Organization
-
A person or a group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives.
-
Organizational Change Management (OCM)
-
Organizational change management is the means by which an organization transitions from the current state to the target state.
-
Organizational Ecosystem
-
The internal elements of an organization (including staff, board, owners, and other stakeholders) together with the organization’s external relationships, such as customers, partners, suppliers, regulators, and competitors.
-
Outcome
-
The result of change, normally affecting real-world behaviour and circumstances. Changes are implemented to achieve outcomes, which are realized as a result of the activities undertaken to facilitate the change.
-
Output
-
The tangible or intangible deliverable of an activity. In PRINCE2, outputs are the specialist products used to enable change.
-
Performance Target
-
The project’s performance target sets the expected success level against which the management of the project will be judged. PRINCE2 Project Management includes performance targets for benefits, cost, time, quality, scope, sustainability, and risk.
-
Persona
-
A fictional, detailed representation of a target user or customer, based on research and data. It typically contains the following information: a picture, a quote, pains, goals, values, and more personal insights, such as personality traits, skills, communication preferences, and brand sympathies. It is used to help teams understand the needs of their target audience.
-
Plan
-
A proposal that outlines the what, where, when, how, and who of the project as a whole (or a subset of its activities). In the PRINCE2 Project Management method, there are the following types of plan: project plan, stage plan, team plan, and exception plan.
-
Planning Horizon
-
The period of time for which it is possible to plan accurately.
-
Portfolio
-
The totality of an organization’s investment (or segment thereof) in the changes required to achieve its strategic objectives.
-
Practice
-
An aspect of project management that must be applied consistently and throughout the project lifecycle. The practices require specific treatment of that aspect of project management for the PRINCE2 Project Management processes to be effective.
-
Principles
-
The PRINCE2 Project Management principles are the guiding obligations that determine whether the project is genuinely being managed using PRINCE2 and ensure effective application and tailoring of PRINCE2 to any project.
-
Probability
-
This is the evaluated likelihood of a particular threat or opportunity actually happening, including a consideration of the frequency with which this may arise.
-
Process
-
A structured set of activities that define the sequence of actions and their inputs and outputs to achieve a specific objective.
-
Product
-
An input or output, whether tangible or intangible, that can be described in advance, created, and tested. PRINCE2 includes four types of products: management products, specialist products, the project product, and external products.
-
Product Breakdown Structure
-
A hierarchy of all the products to be produced during a plan.
-
Product Description
-
A description of a product’s purpose, format, composition, derivation, quality specifications, and development responsibilities.
-
Product Development
-
A function focused on designing, creating, and launching new or changed products and services.
-
Product Flow Diagram
-
A diagram showing the sequence of production and interdependencies of the products listed in a product breakdown structure.
-
Product Management
-
A strategic function that oversees the entire lifecycle of a product.
-
Product Owner (PO)
-
The role assigned to managing the product backlog to get the most value from it by ordering and prioritizing it. In PRINCE2 Agile the PO leads delivery team(s) acting as a servant leader, facilitating collaboration between project governance and delivery.
-
Product Register
-
A component of the project log that identifies the products to be delivered by the project and records their acceptance.
-
Product-Based Planning
-
An approach for developing a comprehensive plan based on the creation and delivery of required outputs. The approach considers prerequisite products, quality requirements, and the dependencies between products.
-
Programme
-
A temporary structure designed to lead multiple interrelated projects and other work in order to progressively achieve outcomes of benefit for one or more organizations.
-
Progress
-
The measure of the achievement of the objectives of a plan.
-
Project
-
A temporary organization that is created for the purpose of delivering one or more business products according to an agreed business case.
-
Project Approach
-
Defines the choice of solution and delivery method that will be used in the project to deliver the business option selected from the business case, considering the operational environment into which the solution must fit.
-
Project Assurance
-
The project board’s responsibilities to assure itself that the project is being conducted correctly. The project board members each have a specific area of focus for project assurance, namely business assurance for the executive, user assurance for the senior user(s), and supplier assurance for the senior supplier(s).
-
Project Baseline
-
The current approved versions of the management products and project products that are subject to change control.
-
Project Board
-
Accountable to the business for the success of the project and has the authority to direct the project within the remit set by the business.
-
Project Brief
-
A statement that describes the purpose, cost, time and performance requirements, and constraints for a project. It is created before the project begins, during the "Starting Up a Project" process, and is used during the "Initiating a Project" process to create the Project Initiation Documentation. It is superseded by the Project Initiation Documentation and not maintained.
-
Project Canvas
-
Another way of presenting information to support business justification. In PRINCE2 Agile one may choose to use the project canvas instead of the business case. Typically, it contains the following: project vision, business value, business options, costs, users, scope, benefits, and major risks.
-
Release
-
A set of features or functionality deployed into use at one time. A release can contain one or more increments and may occur at the end of an iteration or after several iterations.
-
Release Planning
-
The activity of determining when and how groups of features, capabilities, or increments will be delivered into operational use.
-
Requirement
-
A need or expectation that is documented and can be verified.
-
Retrospective
-
A regular event where a team reflects on how it has been working in order to identify improvements.
-
Risk
-
An uncertain event or set of events that, should it occur, will have an effect on the achievement of objectives.
-
Risk Appetite
-
The amount and type of risk that an organization is willing to pursue or retain.
-
Risk Management
-
The systematic application of principles, approaches, and processes to the tasks of identifying and assessing risks, planning and implementing risk responses, and communicating risk management activities with stakeholders.
-
Risk Owner
-
The person assigned to take responsibility for responding to a risk.
-
Scrum
-
An agile framework used to develop, deliver, and sustain complex products through iterative and incremental working.
-
Scrum Master
-
An agile role responsible for ensuring that the Scrum framework is understood and followed, helping the team remove impediments and continuously improve.
-
Servant Leadership
-
A leadership philosophy that focuses on serving others, enabling teams to perform effectively, and removing obstacles to success.
-
Sprint
-
A fixed-length iteration, usually between one and four weeks, during which a usable increment of product is created.
-
Sprint Backlog
-
The set of selected product backlog items together with a plan for delivering them during a sprint.
-
Sprint Goal
-
A short statement describing the objective that the team intends to achieve during a sprint.
-
Stakeholder
-
Any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by the project.
-
Story Mapping
-
A collaborative technique used to visualize user journeys and organize requirements, helping teams understand scope and prioritize delivery.
-
Task Board
-
A visual management tool used by teams to display and monitor the status of work.
-
Technical Debt
-
The implied future cost incurred when choosing a quick or limited solution instead of a more robust approach.
-
Test-Driven Development (TDD)
-
A development technique where automated tests are created before writing the code needed to satisfy those tests.
-
Theme
-
An aspect of project management that must be addressed continually throughout the project lifecycle.
-
Timebox
-
A finite period of time when work is carried out to achieve a goal or objective. The deadline should not be moved; instead, the content is adjusted to meet the fixed timeframe.
-
Tolerance
-
The permissible deviation above and below the plan’s target for benefits, cost, time, quality, scope, sustainability, and risk without needing to escalate the deviation to the next level of management.
-
Transparency
-
One of the key agile values that ensures work, progress, quality, and issues are visible and understood by stakeholders and teams.
-
User Story
-
A tool used to write a requirement in the form of who, what, and why. In PRINCE2 Agile, user stories are typically used to define requirements from the perspective of the user and are commonly recorded in a product backlog.
-
User Story Mapping
-
A collaborative visualization technique that organizes user stories along a user journey, helping teams understand priorities, dependencies, and release planning.
-
Value
-
The worth, importance, or usefulness of something to stakeholders, customers, or the organization. Agile approaches focus on maximizing value through frequent delivery and feedback.
-
Value Stream
-
The sequence of activities required to deliver value to a customer, from initial request through to delivery and realization of benefits.
-
Velocity
-
A measurement of the amount of work completed by a delivery team during an iteration or sprint. Velocity is often used to support forecasting and planning.
-
Vision
-
A description of the desired future state that provides direction, purpose, and motivation for a project or product.
-
Warranty Period
-
A defined period after deployment during which responsibility remains with the supplier or delivery team to address defects and support stabilization.
-
Waste
-
Any activity, process, or resource consumption that does not add value to the customer or contribute to desired outcomes. Removing waste is a key principle of Lean thinking.
-
Work In Progress (WIP)
-
Work that has been started but not yet completed. Limiting work in progress is a key technique used by flow-based methods such as Kanban to improve throughput and identify bottlenecks.
-
Work Package
-
Work assigned to a delivery team requiring the creation of one or more products. It defines expectations, constraints, quality requirements, and reporting arrangements.
-
Work Package Description
-
The set of information relevant to the delivery of one or more products. It contains descriptions of the activities to be performed, the resources involved, relevant product descriptions, and details of any constraints on production.
-
Zero Defects
-
A quality mindset focused on preventing defects rather than finding and correcting them later. It emphasizes building quality into products and processes from the outset.
Back to top