Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

PMP Exam Prep > Agile Vocab > Flashcards

Agile Vocab Flashcards

1
Q

A3

A

way of thinking and systematic problem-solving process that collects the pertinent information on a single A3-size sheet of paper

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
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
3
Q

agile

A

term used to describe a mindset of values and principles as set forth in the Agile Manifesto

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

agile coach

A

individual with knowledge and experience in agile who can train, mentor, and guide organizations and teams through their transformation

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

agile life cycle

A

approach that is both interactive and incremental to refine work items and deliver frequently

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

agile manifesto

A

original and official definition of agile values and principles

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

agile mindset

A

way of thinking and behaving underpinned by the four values and twelve principles of the agile manifesto

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

agile practitioner, agilist

A

person embracing the agile mindset who collaborates with like-minded colleagues in cross-function teams

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
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
10
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
11
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
12
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
13
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
14
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
15
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
16
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
17
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
18
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
19
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
20
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
21
Q

cadence, timebox

A

rhythm of execution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
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
23
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
24
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
25
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
26
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
27
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
28
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
29
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
30
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
31
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
32
Q

double loop learning

A

process that challenges underlying values and assumptions in order to better elaborate root causes and devise improved countermeasures rather than focusing only on symptoms

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

Dynamic Systems Development Method (DSDM)

A

agile project delivery framework

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

evolutionary value delivery (EVO)

A

agile method with unique focus on delivering multiple measurable value requirements to stakeholders

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

eXtreme programming (XP)

A

agile software development method that leads to higher quality software, a greater responsiveness to changing customer requirements, and more frequent releases in shorter cycles

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

feature-driven development

A

lightweight agile software development method driven from the perspective features valued by clients

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

fit for purpose

A

product that is suitable for its intended purpose

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

flow master, Scrum master

A

the coach of the development team and process owner in the Scrum framework. Removes obstacles, facilitates productive events, and defends the team from disruptions

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

framework

A

basic system or structure of ideas or facts that supports an approach

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

functional requirement

A

specific behavior that a product or service should perform

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

functional specification

A

specific function that a system or application is required to perform.

42
Q

Hoshin Kanri

A

strategy or policy deployment method

43
Q

hybrid approach

A

combination of two or more agile and non-agile elements, having a non-agile end result

44
Q

IDEAL

A

organizational improvement model that is named for the five phrases it describes: imitating, diagnosing, establishing, acting, and learning

45
Q

impact mapping

A

strategic planning technique that acts as a roadmap to the organization while building new products

46
Q

increment

A

a functional, tested, and accepted deliverable that is a subset of the overall project outcome

47
Q

incremental life cycle

A

approach that provides finished deliverables that the customer may be able to use immediately

48
Q

information radiator

A

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

49
Q

I-shaped

A

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

50
Q

iterative life cycle

A

an approach that allows feedback for unfinished work to improve and modify that work

51
Q

Kaizen Events

A

events aimed at improvement of the system

52
Q

Kanban Board

A

visualization tool that enables improvements to the flow of work by making bottlenecks and work quantities visible

53
Q

Kanban Method

A

agile method inspired by the original Kansan inventory control system and used specifically for knowledge work

54
Q

large scale Scrum (LeSS)

A

product development framework that extends Scrum with scaling guidelines while preserving the original purposes of Scrum

55
Q

Lean Software Development (LSD)

A

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

56
Q

life cycle

A

process through which a product is imagined, created, and put into use

57
Q

mobbing

A

technique in which multiple team members focus simultaneously and coordinate their contributions on a particular work item

58
Q

organizational bias

A

preferences of an organization non a set of scales characterized by the following core values: exploration versus execution, speed versus stability, quantity versus quality, and flexibility versus predictability

59
Q

organizational change management

A

a comprehensive, cyclic, and structured approach for transitioning individuals, groups, and organizations from the current state to a future state with intended business benefits

60
Q

pair work, pairing

A

technique of pairing two team members to work simultaneously on the same work item

61
Q

pair programming

A

pair work that is focused on programming

62
Q

personas

A

archetype user representing a set of similar end users described with their goals, motivations, and representative personal characteristics

63
Q

pivot

A

planned course correction designed to test a new hypothesis about the product or strategy

64
Q

plan-do-check-act (PDCA)

A

an interactive management method used in organizations to facilitate the control and continual improvement of processes and products

65
Q

plan-driven approach, predictive approach

A

approach to work management that utilizes a work plan and management of that work plan throughout the lifecycle of a project

66
Q

predictive life cycle

A

more traditional approach, with bulk of planning occurring up-front, then executing in a single pass

67
Q

project management office

A

management structure that standardizes the project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques

68
Q

product owner

A

person responsible for maximizing the value of the product and who is ultimately responsible and accountable for the end product that is built

69
Q

progressive elaboration

A

iterative process of increasing the level of detail in a project management plan as greater amounts of information and more accurate estimates become available

70
Q

refactoring

A

product quality technique whereby the design of a product is improved by enhancing its maintainability and other desired attributes without altering its expected behavior

71
Q

retrospective

A

regularly occurring workshop in which participants explore their work and results in order to improve both process and product

72
Q

rolling wave planning

A

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

73
Q

Scaled Agile Framework (SAFe)

A

knowledge base of integrated patterns for enterprise-scale lean-agile development

74
Q

Scrum

A

agile framework for developing and sustaining complex products, with specific roles, events, and artifacts

75
Q

Scrumban

A

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

76
Q

Scrum Board

A

information radiator that is utilized to manage the product and sprint backlogs and show the flow of work and its bottlenecks.

77
Q

Scrum of Scrums

A

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.

78
Q

Scrum team

A

describes the combo of development team, Scrum master, and product owner used in Scrum

79
Q

Self-organizing team

A

a cross-function team in which people fluidly assume leadership as needed to achieve the team’s objectives

80
Q

servant leadership

A

practice of leading through service to the team, by focusing on understanding and addressing the needs and development of team members in order to enable the highest possible team performance

81
Q

service request manager

A

person responsible for ordering service requests to maximize value in a continuous flow or Kansan environment. equivalent to product owner.

82
Q

siloed organization

A

organization structured in such a way that it only manages to contribute a subset of aspects required for delivering value to customers

83
Q

single loop learning

A

practice of attempting to solve problems by just using specific predefined methods, without challenging the methods in light oof experience

84
Q

smoke testing

A

practice of using a lightweight set of tests to ensure that the most important functions of the system under development work as intended

85
Q

specification by example (SBE)

A

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

86
Q

spike

A

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

87
Q

sprint

A

describes a time boxed iteration in scrum

88
Q

sprint backlog

A

list of work items identified by the Scrum team to be completed during the Scrum sprint

89
Q

sprint planning

A

collaborative event in Scrum in which the Scrum team plans the work for the current sprint

90
Q

story point

A

unit-less measure used in relative user story estimation techniques

91
Q

swarming

A

technique in which multiple team members focus collectively on resolving a specific impediment

92
Q

technical debt

A

deferred cost of work not done at an earlier point in the product life cycle

93
Q

test-driven development

A

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

94
Q

iteration, timebox

A

a fixed period of time

95
Q

T-shaped

A

refers to a person with one deep area of specialization and broad ability in the rest of the skills required by the team

96
Q

user story

A

brief description of deliverable value for a specific user. it is a promise for a conversation to clarify details

97
Q

user story mapping

A

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

98
Q

UX design

A

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

99
Q

value stream

A

an organization construct that focuses on the flow of value to customers through the delivery of specific products or services

100
Q

value stream mapping

A

a lean enterprise technique used to document, analyze, and improve the flow of information or materials required to produce a product or service for a customer

PMP Exam Prep (3 decks)

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