Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

PMP Exam Prep > Agile Vocab > Flashcards

Agile Vocab Flashcards

1
Q

acceptance test-driven development (ATDD)

A

method of collaboratively creating acceptance test criteria that are used to create acceptance tests before delivery begins

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

agile unified process

A

simplistic and understandable approach to developing business application software using agile techniques and concepts.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

anti-pattern

A

known, flawed pattern of work that is not advisable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

automated code quality analysis

A

scripted testing of code base for bugs and vulnerabilites

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

backlog, product backlog

A

ordered list of user-centric requirements that a team maintains for a product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

backlog refinement

A

progressive elaboration of project requirements and/or the ongoing activity in which the team collaboratively reviews, updates, and writes requirements to satisfy the need of the customer request

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

behavior-driven development (BDD)

A

system design and validation practice that uses test-first principles and English-like scripts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

blended agile

A

two or more agile frameworks, methods, elements, or practices used together such as Scrum practiced in combination with XP and Kansan Method

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

blocker, impediment

A

obstacle that prevents the team from achieving its objectives

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

broken comb, paint drip

A

refers to a person with various depths of specialization in multiple skills required by the team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

burndown chart

A

graphical representation of the work remaining versus the time left in a timebox

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

burnup chart

A

graphical representation of the work completed toward the release of a product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

business requirement documents (BRD)

A

listing of all requirements for a specific project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

cadence, timebox

A

rhythm of execution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

collective code ownership

A

project acceleration and collaboration technique whereby any team member is authorized to modify any project work product or deliverable, thus emphasizing team-wide ownership and accountability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

continuous delivery

A

practice of delivering feature increments immediately to customers, often through the use of small batches of work and automation technology

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

continuous integration

A

practice in which each team member’s work products are frequently integrated and validated with one another

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

cross-function team

A

team that includes practitioners with all the skills necessary to deliver valuable adaptability to a particular circumstance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Crystal Family of Methodologies

A

collection of lightweight agile software development methods focused on adaptability to a particular circumstance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

daily Scrum

A

brief, daily collaboration meeting in which the team reviews progress from the previous day, declares intentions for the current day, and highlights any obstacles encountered or anticipated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

definition of done (DoD)

A

team’s checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

definition of ready (DoR)

A

team’s checklist for a user-centric requirement that has all the information the team needs to be able to begin working on it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

DevOps

A

collection of practices for creating a smooth flow of delivery by improving collaboration between development and operations staff

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

disciplined agile (DA)

A

process decision framework that enables simplified process decisions around incremental and iterative solution delivery

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
double loop learning
process that challenges underlying values and assumptions in order to better elaborate root causes and devise improved countermeasures rather than focusing only on symptoms
26
Dynamic Systems Development Method (DSDM)
agile project delivery framework
27
evolutionary value delivery (EVO)
agile method with unique focus on delivering multiple measurable value requirements to stakeholders
28
eXtreme programming (XP)
agile software development method that leads to higher quality software, a greater responsiveness to changing customer requirements, and more frequent releases in shorter cycles
29
feature-driven development
lightweight agile software development method driven from the perspective features valued by clients
30
fit for purpose
product that is suitable for its intended purpose
31
flow master, Scrum master
the coach of the development team and process owner in the Scrum framework. Removes obstacles, facilitates productive events, and defends the team from disruptions
32
Hoshin Kanri
strategy or policy deployment method
33
hybrid approach
combination of two or more agile and non-agile elements, having a non-agile end result
34
IDEAL
organizational improvement model that is named for the five phrases it describes: imitating, diagnosing, establishing, acting, and learning
35
impact mapping
strategic planning technique that acts as a roadmap to the organization while building new products
36
incremental life cycle
approach that provides finished deliverables that the customer may be able to use immediately
37
information radiator
visible, physical display that provides information to the rest of the organization enabling up-to-the-minute knowledge sharing without having to disturb the team
38
I-shaped
refers to a person with a single deep area of specialization and no interest or skill in the rest of the skills required by the team
39
iterative life cycle
an approach that allows feedback for unfinished work to improve and modify that work
40
Kaizen Events
events aimed at improvement of the system
41
Kanban Method
agile method inspired by the original Kansan inventory control system and used specifically for knowledge work
42
large scale Scrum (LeSS)
product development framework that extends Scrum with scaling guidelines while preserving the original purposes of Scrum
43
Lean Software Development (LSD)
Adaptation of lean manufacturing principles and practices to the software development domain and is based on a set of principles and practices for achieving quality, speed, and customer alignment
44
mobbing
technique in which multiple team members focus simultaneously and coordinate their contributions on a particular work item
45
organizational change management
a comprehensive, cyclic, and structured approach for transitioning individuals, groups, and organizations from the current state to a future state with intended business benefits
46
pair work, pairing
technique of pairing two team members to work simultaneously on the same work item
47
personas
archetype user representing a set of similar end users described with their goals, motivations, and representative personal characteristics
48
pivot
planned course correction designed to test a new hypothesis about the product or strategy
49
plan-do-check-act (PDCA)
an interactive management method used in organizations to facilitate the control and continual improvement of processes and products
50
plan-driven approach, predictive approach
approach to work management that utilizes a work plan and management of that work plan throughout the lifecycle of a project
51
predictive life cycle
more traditional approach, with bulk of planning occurring up-front, then executing in a single pass
52
product owner
person responsible for maximizing the value of the product and who is ultimately responsible and accountable for the end product that is built
53
progressive elaboration
iterative process of increasing the level of detail in a project management plan as greater amounts of information and more accurate estimates become available
54
refactoring
product quality technique whereby the design of a product is improved by enhancing its maintainability and other desired attributes without altering its expected behavior
55
retrospective
regularly occurring workshop in which participants explore their work and results in order to improve both process and product
56
rolling wave planning
an interactive planning technique in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level
57
Scaled Agile Framework (SAFe)
knowledge base of integrated patterns for enterprise-scale lean-agile development
58
Scrum
agile framework for developing and sustaining complex products, with specific roles, events, and artifacts
59
Scrumban
management framework that emerges when teams employ Scrum as the chose way of working and us the Kansan Method as a lens through which to view, understand, and continuously improve how they work
60
Scrum Board
information radiator that is utilized to manage the product and sprint backlogs and show the flow of work and its bottlenecks.
61
Scrum of Scrums
technique to operate Scrum at scale for multiple teams working on the same product, coordinating discussions of progress on their interdependencies, and focusing on how to integrate the delivery of software, especially in areas of overlap.
62
Scrum team
describes the combo of development team, Scrum master, and product owner used in Scrum
63
Self-organizing team
a cross-function team in which people fluidly assume leadership as needed to achieve the team’s objectives
64
service request manager
person responsible for ordering service requests to maximize value in a continuous flow or Kansan environment. equivalent to product owner.
65
siloed organization
organization structured in such a way that it only manages to contribute a subset of aspects required for delivering value to customers
66
single loop learning
practice of attempting to solve problems by just using specific predefined methods, without challenging the methods in light oof experience
67
smoke testing
practice of using a lightweight set of tests to ensure that the most important functions of the system under development work as intended
68
specification by example (SBE)
collaborative approach to defining requirements and business-oriented functional tests for software products based on capturing and illustrating requirements using realistic examples instead of abstract statements
69
spike
short time interval within a project, usually of a fixed length, during which a team conducts research or prototypes an aspect of a solution to prove its viability
70
sprint backlog
list of work items identified by the Scrum team to be completed during the Scrum sprint
71
story point
unit-less measure used in relative user story estimation techniques
72
swarming
technique in which multiple team members focus collectively on resolving a specific impediment
73
technical debt
deferred cost of work not done at an earlier point in the product life cycle
74
test-driven development
a technique where tests are defined before work is begun, so that work in progress is validated continuously, enabling work with a zero defect mindset
75
T-shaped
refers to a person with one deep area of specialization and broad ability in the rest of the skills required by the team
76
user story
brief description of deliverable value for a specific user. it is a promise for a conversation to clarify details
77
user story mapping
a visual practice for organizing work into a useful model to help understand the sets of high-value features to be created over time, identify omissions in the backlog, and effectively plan releases that deliver value to users
78
UX design
process of enchancing the user experience by focusing on improving the usability and accessibility to be found in the interaction between the user and the product
79
value stream
an organization construct that focuses on the flow of value to customers through the delivery of specific products or services

PMP Exam Prep (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions