Question 1

PRINCE2 Agile

Accepted Answer

PRINCE2 methodology blended with Agile delivery techniques.

Question 2

PRINCE2 Process Model

Accepted Answer

A structured, linear approach for managing a project from start to finish.

Question 3

Agile Delivery

Accepted Answer

A iterative, flexible approach emphasizing collaboration, customer feedback, and small, rapid changes.

Question 4

Scrum

Accepted Answer

An iterative and incremental agile software development methodology.

Question 5

Kanban

Accepted Answer

A scheduling system for lean and just-in-time production.

Question 6

Cynefin Framework

Accepted Answer

A conceptual framework used to aid decision-making.

Question 7

Lean Startup

Accepted Answer

A methodology for developing businesses and products based on 'validated learning'.

Question 8

Crystal Methods

Accepted Answer

A family of Agile methodologies developed by Alistair Cockburn.

Question 9

Customer Liaison

Accepted Answer

An important role in Agile projects ensuring customer collaboration.

Question 10

Sprint

Accepted Answer

A time-boxed iteration in Scrum and Agile methodologies.

Question 11

User Story

Accepted Answer

A tool used in Agile software development to capture a description of a software feature from an end-user perspective.

Question 12

Burndown Chart

Accepted Answer

A visual representation of work left to do versus time in Agile methodologies.

Question 13

Stand-Up Meeting

Accepted Answer

A daily meeting in Agile methods, specifically Scrum, to update the team on progress.

Question 14

Sprint Backlog

Accepted Answer

A list of tasks to be completed during a Sprint in Scrum.

Question 15

Cumulative Flow Diagram

Accepted Answer

A tool used in Agile methodologies to visualize and track project progress.

Question 16

Product Backlog

Accepted Answer

A prioritized list of features to be developed for a product or system.

Question 17

Backlog Refinement

Accepted Answer

The process of updating and maintaining the product backlog in Agile methodologies.

Question 18

Retrospective

Accepted Answer

A team meeting at the end of a project or process to reflect on what happened.

Question 19

Velocity

Accepted Answer

A measure of the amount of work a Team can tackle during a single Sprint.

Question 20

Estimation

Accepted Answer

The process of predicting the most realistic amount of effort required to develop or maintain software.

Question 21

Agile Coach

Accepted Answer

A person responsible for creating an environment for agility to thrive.

Question 22

Definition of Done

Accepted Answer

A shared understanding of what it means for work to be complete.

Question 23

MoSCoW Prioritization

Accepted Answer

A technique used to reach a common understanding with stakeholders on the importance of the delivery of each requirement.

Question 24

WIP Limit

Accepted Answer

Work-in-progress limit, a strategy of limiting the amount of work in process in order to improve flow.

Question 25

Epic

Accepted Answer

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

Question 26

Spike

Accepted Answer

A story that cannot be estimated until a development team runs a time-boxed investigation.

Question 27

Acceptance Criteria

Accepted Answer

The conditions that a software product must satisfy to be accepted by a user or customer.

Question 28

Burnup Chart

Accepted Answer

A graphical representation of work done versus time.

Question 29

Feature

Accepted Answer

A distinct element of functionality that can provide value for a customer.

Question 30

Timebox

Accepted Answer

A fixed duration of time in which a specific activity occurs or a specific objective is pursued.

Question 31

Workstream

Accepted Answer

A sequence of tasks completed in parallel to other sequences, from the start to the end of a project.

Question 32

Adaptive Planning

Accepted Answer

A planning strategy that acknowledges the uncertainty of the project and prepares for it by remaining flexible and adaptable.

Question 33

Agile Manifesto

Accepted Answer

A proclamation that articulates four key values and twelve principles that its authors believe software developers should use to guide their work.

Question 34

Cross-Functional Team

Accepted Answer

A group of people with different functional expertise working toward a common goal.

Question 35

Fixed Date Agile

Accepted Answer

An approach to software development where the deadline for delivery is fixed but the scope is flexible.

Question 36

Planning Poker

Accepted Answer

A consensus-based estimating technique in Agile methodologies.

Question 37

Task Board

Accepted Answer

A project management tool used to visualize the status of different tasks.

Question 38

Feedback Loop

Accepted Answer

A method of continually gathering and integrating feedback in Agile methodologies.

Question 39

Daily Scrum

Accepted Answer

A short stand-up meeting meant to quickly inform everyone of what's going on across the team.

Question 40

Sprint Review

Accepted Answer

A meeting at the end of the Sprint where the team demonstrates what they completed during the Sprint.

Question 41

Product Owner

Accepted Answer

A role in Scrum responsible for maximizing the value of the product and the work of the Development Team.

Question 42

Scrum Master

Accepted Answer

A facilitator for an Agile development team, ensuring adherence to Scrum values and practices.

Question 43

Development Team

Accepted Answer

A cross-functional group of professionals who do the work of delivering a potentially releasable increment of product at the end of each Sprint.

Question 44

Product Increment

Accepted Answer

The sum of all the Product Backlog items completed during a Sprint and all previous Sprints.

Question 45

Sprint Zero

Accepted Answer

A pre-step to any Agile Scrum project where certain activities happen before the first Sprint.

Question 46

Burnout

Accepted Answer

In Agile, this is the process of tracking how much work is left to be done by burning down tasks.

Question 47

Value-Driven Delivery

Accepted Answer

An Agile principle that emphasizes delivering valuable features to customers with a short feedback cycle.

Question 48

Story Points

Accepted Answer

A unit of measure for expressing an estimate of the overall effort required to fully implement a product backlog item or any other piece of work.

Question 49

Chicken and Pigs

Accepted Answer

Terms used in Agile development to describe two types of project members based on a farming metaphor.

Question 50

Affinity Estimation

Accepted Answer

An agile estimation technique to size user stories.

Question 51

Release Planning

Accepted Answer

A longer-term planning process within Agile development.

Question 52

Agile Modeling

Accepted Answer

A practice-based methodology for effective modeling and documenting software-based systems.

Question 53

Refactoring

Accepted Answer

A disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior.

Question 54

Time & Materials

Accepted Answer

A type of contract where the customer agrees to pay the contractor based upon the time spent to perform the work, and for materials used in the construction.

Question 55

Fixed Price

Accepted Answer

A pricing arrangement where a specific amount of money is agreed upon as the total payment for a project.

Question 56

Servant Leadership

Accepted Answer

A leadership philosophy where the goal of the leader is to serve the team members.

Question 57

Test-Driven Development

Accepted Answer

A software development process where test cases are developed, and each case is considered passed only when the test passes.

Question 58

Behavior-Driven Development

Accepted Answer

A software development methodology in which an application is specified and designed by describing how its behavior should appear to an outside observer.

Question 59

Definition of Ready

Accepted Answer

A shared understanding by the Scrum Team on what it takes for a Product Backlog Item to be ready for development.

Question 60

Adaptive Leadership

Accepted Answer

A leadership framework that helps individuals and organizations adapt and thrive in challenging environments.

Question 61

The Agile Triangle

Accepted Answer

A model that defines value in Agile projects in terms of three dimensions: Quality/Value, Time-to-Market/Speed, and Scope/Innovation.

Question 62

Story Mapping

Accepted Answer

A method for arranging user stories to create a more holistic view of how they fit into the overall user experience.

Question 63

Innovation Games

Accepted Answer

A product development method in which customers play games to express their needs, wishes, and priorities.

Question 64

Pair Programming

Accepted Answer

An Agile software development technique in which two programmers work together at one workstation.

PRINCE2 Agile Foundation