Brainscape's Knowledge GenomeTM

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


See full index

PMI-ACP > Glossary of Agile Terms > Flashcards

Glossary of Agile Terms Flashcards

1
Q

ACP

A

Agile Certified Practitioner

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

Acceptance Test Driven Development

A

A method used to communicate with business customers, developers, and testers before coding begins.

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

Active Listening

A

To focus on what is said and provide feedback to communicate understanding.

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

Adaptive Leadership

A

A leadership style that helps teams thrive and overcome challenges throughout a project.

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

Affinity Estimation

A

A method used to quickly place user stories into a comparable-sized group.

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

Agile

A

To develop a goal through periodic experimentation in order to fulfill the need of a complex decision.

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

Agile Adaption

A

To adapt the project plan continuously through retrospectives in order to maximize value creation during the planning process.

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

Agile Coaching

A

To help achieve goals that is either personal or organizational.

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

Agile Experimentation

A

To use the empirical process, observation, and spike introduction while executing a project to influence planning.

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

Agile Mentoring

A

To pass on and teach based on experience, knowledge, and skills to other individuals in the team or that work for the organization.

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

Agile Methodologies

A

A way to complete a goal effectively and efficiently. Examples of Agile Methodologies include XP, Scrum, and Lean.

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

Agile Modeling

A

A workflow depiction of a process or system a team can review before it is turned into code. Stakeholders should understand the model.

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

Agile Planning

A

The most important aspect of the Agile project. Planning happens at multiple levels such as strategic, release, iteration, and daily. Planning must happen up-front and can change throughout the project.

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

Agile Practices

A

To make use of the Agile principles through activities.

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

Agile Projects

A

A project that occurs based on the Agile Manifesto and Agile Principles.

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

Agile Smells

A

Symptoms of problems that affect Agile teams and projects.

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

Agile Space

A

A space that allows team members to establish collaboration, communication, transparency, and visibility.

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

Agile Themes

A

Themes used to help the team focus on the functions of iteration.

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

Agile Tooling

A

To increase team morale with software or artifacts.

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

Analysis

A

To develop possible solutions by studying the problem and its underlying need and to understand the information provided.

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

Approved Iterations

A

After the deadline of iteration is reached, the team and stakeholders conduct a meeting for approval. Stakeholders approve the iteration if the backlog used supports the product increment.

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

Architectural Spikes

A

Spikes that relate to any area of a system, technology, or application domain that is unknown.

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

Artifact

A

A process or work output Ex. Document, Code

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

ASD

A

Exhibits continuous adaptation to the project and its processes with characteristics that include: mission focused, feature based, iterative, time-boxed, risk driven, and change tolerant.

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

Automated Testing Tools

A

These tools allow for efficient and strong testing. Examples: Peer Reviews, Periodical Code-Reviews, Refactoring, Unit Tests, Automatic and Manual Testing.

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

Being Agile

A

To work in a responsive way to deliver the products or services a customer needs and when they want the products or services.

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

Brainstorming

A

An effective and efficient way of gathering ideas within a short period of time from a group.

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

Burn-Down Chart

A

A chart used to display progress during and at the end of iteration. “Burning down” means the backlog will lessen throughout the iteration.

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

Burn Rate

A

The rate of resources consumed by the team; also cost per iteration.

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

Burn-Up Chart

A

A chart that displays completed functionality. Progress will trend upwards, as stories are completed. Only shows complete functions, it is not accurate at predicting or showing work-in-progress.

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

CARVER

A

An acronym to measure the goals and mission of the project with each letter meaning: Criticality, Accessibility, Return, Vulnerability, Effect, and Recognizeability.

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

Ceremony

A

A meeting conducted during an Agile project that consists of daily stand-up, iteration planning, iteration review, and iteration retrospective.

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

Change

A

To change requirements that increase value to the customer.

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

Charter

A

A document created during initiation that formally begins the project. The document includes the project’s justification, a summary level budget, major milestones, critical success factors, constraints, assumptions, and authorization to do it.

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

Chicken

A

An individual involved but not committed to an Agile project.

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

Coach

A

A team role that keeps the team focused on learning and the process.

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

Collaboration

A

A method of cooperation among individuals to achieve a common goal.

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

Collective Code Ownership

A

The entire team together is responsible for 100% of the code.

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

Collocation

A

The entire team is physically present, working in one room.

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

Common Cause

A

An issue solved through trend analysis because the issue is systematic.

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

Communication

A

To share smooth and transparent information of needs.

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

Command & Control

A

Decisions created by higher up individuals in the organization and handed over to the team.

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

Compliance

A

To meet regulations, rules, and standards.

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

Cone of Silence

A

An environment for the team that is free of distractions and interruptions.

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

Conflict

A

Disagreements in certain areas between individuals.

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

Conflict Resolution

A

An agreement made after a conflict.

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

Continuous Improvement

A

To ensure that self-assessment and process improvement occurs frequently to improve the product.

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

Continuous Integration

A

To consistently examine a team member’s work. To build, and test the entire system.

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

Coordination

A

To organize work with the goal of higher productivity and teamwork.

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

Cost Performance Index (CPI)

A

To measure the cost spent on a project and its efficiency. Earned Value / Actual Cost = CPI

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

Cross-Functional Team

A

Teams that consist of members who can complete various functions to achieve a common goal. Team members are able to do more than one role in a project.

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

Crystal Family

A

An adaptable approach that focuses on interaction between people and processes that consists of families that vary based on team size, system criticality, and project priorities.

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

Cumulative Flow Diagram

A

A chart that displays feature backlog, work-in-progress, and completed features.

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

Customer

A

The end-user who determines and emphasizes business values.

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

Customer-Valued Prioritization

A

To deliver the maximum customer value early in order to win customer loyalty and support.

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

Cycle Time

A

The time needed to complete a feature (user story).

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

Daily Stand Up

A

A brief meeting where the team shares the previous day’s achievements, plans to make achievements, obstacles, and how to overcome the obstacles.

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

Decide As Late As Possible

A

To postpone decisions to determine possibilities and make the decision when the most amount of knowledge is available.

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

DEEP

A

The qualities of a product backlog which include: detailed, estimate-able, emergent, and prioritized.

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

Deliverables

A

A tangible or intangible object delivered to the customer. Ex. Document, Pamphlet, Report

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

Disaggregation

A

To separate epics or large stories into smaller stories.

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

Dissatisfaction

A

The lack of satisfaction among workers such as, work conditions, salary, and management-employee relationships. Factors known as demotivators.

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

Distributive Negotiation

A

To reach a deal through tactics so both parties receive the highest amount of value possible.

64
Q

Done

A

When work is complete, and meets the following criteria: complies, runs without errors, and passes predefined acceptance and regression tests.

65
Q

Dot Voting

A

A system of voting where people receive a certain number of dots to vote on the options provided.

66
Q

Dynamic Systems Development Model (DSDM)

A

A model that provides a comprehensive foundation for planning, managing, executing, and scaling agile and iterative software development projects based on nine principles that involve business needs/value, active user involvement, empowered teams, frequent delivery, integrated testing, and stakeholder collaboration.

67
Q

Earned Value Management (EVM)

A

Earned Value Management, works well at iteration. It is a method to measure and communicate progress and trends at the current stage of the project.

68
Q

Emergent

A

Stories that grow and change overtime as other stories reach completion in the backlog.

69
Q

Emotional Intelligence

A

An individual’s skill to lead and relate to other team members.

70
Q

Epic Story

A

A large story that spans iterations, then disaggregated into smaller stories.

71
Q

Escaped Defects

A

Defects reported after the delivery by the customer.

72
Q

Expectancy Theory

A

An individual chooses to behave in a particular way over other behaviors because of the expected results of the chosen behavior.

73
Q

Exploratory Testing

A

To inquire how software works with the use of test subjects using the software and asking questions about the software.

74
Q

Extreme Persona

A

A team-manufactured persona that exaggerates to induce requirements a standard persona may miss.

75
Q

eXtreme Programming (XP)

A

A methodology in Agile with one-week iterations and paired development.

76
Q

Feature-Driven Development (FDD)

A

A comprehensive model and list of features included in the system before the design work begins.

77
Q

Feature

A

A group of stories that deliver value to the customers.

78
Q

Feedback

A

Information or responses towards a product or project used to make improvements.

79
Q

Fibonacci Sequence

A

A sequence of numbers used in Agile estimating, 0, 1, 2, 3, 5, 8, 13, 20, 40, 100.

80
Q

Finish Tasks One by One

A

Tasks must be finished in all iterations to meet the “Definition of Done” requirements as a way to track progress and allow frequent delivery.

81
Q

Fishbone Diagram

A

A root cause diagram.

82
Q

Five Whys

A

The root causes analysis technique that asks WHY five times. The problem is looked into deeper each time WHY is asked. Toyota developed this technique.

83
Q

Fixed Time Box

A

Assigned tasks prioritized for completion based on an estimated number of days. Top priorities are usually completed first.

84
Q

Focus

A

To stay on task, and is facilitated by the scrum master or coach.

85
Q

Force Field Analysis

A

To analyze forces that encourages or resists change.

86
Q

Functionality

A

An action the customer must see and experience from a system, which will add value to the customer.

87
Q

Grooming

A

To clean up the product backlog by removal of items, disaggregation of items, or estimation of items.

88
Q

Ground Rules

A

Unwritten rules decided and followed by team members.

89
Q

Herzberg’s Hygiene Theory

A

A theory that states factors in the workplace create satisfaction and dissatisfaction in relation to the job.

90
Q

High-Bandwidth Communication

A

Face-to-face communication that also includes non-verbal communication.

91
Q

High Performing Team

A

This team reaches maximum performance by creation of clear, detailed goals, open communication, accountability, empowerment, use of the participatory decision model, and the team consists of twelve dedicated members or less.

92
Q

Ideal Time

A

The amount of time needed to complete an assignment without distractions or interruptions.

93
Q

Incremental Delivery

A

Functionality conveyed in small phases.

94
Q

Incremental Project Releases

A

To build upon the prior release of a goal, outcome, or product, not all requirements are met, but after all releases, the requirements will be met.

95
Q

Information Radiator

A

Artifacts used to help maintain transparency of a project status to team members and stakeholders.

96
Q

Information Refrigerator

A

Information that is not transparent or useful to the team and stakeholders.

97
Q

Innovation Games

A

Practice used to induce requirements from product, owners, users, and stakeholders.

98
Q

Integrative Negotiation

A

To reach an agreement collaboratively that creates more value for both parties by a win-win solution.

99
Q

Interaction

A

Face-to-Face communication

100
Q

IRR

A

Internal Rate of Return- a discount rate that makes the net present value of all cash flows from a project equal to zero. Used to determine potential profitability of project or investment.

101
Q

Intraspectives

A

To inspect within, during a meeting with the Agile team to review practices, usually when a problem or issue occurs.

102
Q

Intrinsic Schedule Flaw

A

Poor estimation that occurs at the beginning of iteration.

103
Q

INVEST

A

The benefits of good user stories, which include: Independent, Negotiable, Valuable, Estimate-able, Small, and Testable.

104
Q

Iteration Backlog

A

Work to complete in a particular iteration.

105
Q

Iteration

A

Work cycle, Scrum uses 2-4 weeks, XP uses 1 week.

106
Q

Iteration H

A

Iteration used to prepare the launch of software, and to test software.

107
Q

Iteration 0

A

Iteration to complete tasks before the development work occurs, for technical and architectural spikes and to gather requirements into the backlog.

108
Q

Iteration Retrospective

A

A meeting used in Scrum, the team discusses ways to improve after work is completed.

109
Q

Just-In-Time

A

Used to minimize inventory cost by materials delivered before they are required.

110
Q

Kaizen

A

Based on Japanese management philosophy, to continue improvement through small releases.

111
Q

Kanban

A

A signal used to advance transparency of work-in-progress, a new task can begin once a previous one is complete.

112
Q

Kanban Board

A

A chart that shows workflow stages to locate work-in-progress.

113
Q

Kano Analysis

A

An analysis of product development and customer satisfaction based on needs fulfilled/not fulfilled vs. satisfaction/dissatisfaction.

114
Q

Last Responsible Moment

A

To make decisions as late as possible in order to preserve all possible options.

115
Q

Lean Methodology

A

To eliminate waste, an Agile method derived from manufacturing.

116
Q

Little’s Law

A

The law that limits work-in-progress efficiently with development of an appropriate cycle time.

117
Q

Low Performing Team

A

This team has a lack of trust, no accountability, fear of conflict, less commitment, and less attention to details and results.

118
Q

Lean Software Development (LSD)

A

This methodology focuses on the “Value Stream” to deliver value to customers. The goal is to eliminate waste by focusing on valuable features of a system and to deliver the value in small batches. Principles of Lean include: elimination of waste, amplify learning, to decide late as possible, deliver as fast as possible, empowerment of the team, to build in integrity, and to see the whole.

119
Q

Maslow’s Hierarchy of Needs

A

This theory suggests the interdependent needs (motivators) of people based on five levels in this order: Physiological, Safety & Security, Social, Esteem, and Self-Actualization.

120
Q

Metaphor

A

To explain how a project will be completed successfully to stakeholders by use of real-world examples of systems and components.

121
Q

Minimal Viable Product (MVP)

A

A product with only the essential features delivered to early adopters to receive feedback.

122
Q

Minimal Marketing Feature (MMF)

A

The smallest feature of a product that provides value to the end-user.

123
Q

Monopoly Money

A

To give fake money to business features in order to compare the relative priority of those features.

124
Q

MoSCoW Analysis

A

An analysis used to help stakeholders understand the importance of each requirement delivered. MoSCoW is the acronym for Must have, Should have, Could have, and Would like to have.

125
Q

Negotiation

A

To reach an agreement between two or more parties to resolve a conflict.

126
Q

Negotiable

A

Anything opened to discussion.

127
Q

NPV

A

Net Present Value- A value that compares the amount invested today to the present value of future cash receipts from the investment.

128
Q

Osmotic Communication

A

To communicate by sharing an environment.

129
Q

Pair Programming

A

When developers work together in XP Practice

130
Q

Pareto Principle

A

Known as the 80/20 rule. For Agile projects, it means that 80% of all development should be spent on the top 20% of the features the customers need.

131
Q

Parking Lot

A

A storage place for ideas that distract from the main goal during a meeting.

132
Q

Participatory Decision Models

A

To have stakeholder’s involvement in decision making with techniques such as a simple vote.

133
Q

Persona

A

A depiction of the customer of system with applicable details about usage.

134
Q

Personnel Loss

A

When an employer faces the loss of a human resource through death, injury, or disability of an employee.

135
Q

Pig

A

A committed individual impacted by the outcome.

136
Q

Plan-Do-Check-Act

A

Work cycle in smaller, quick iterations than traditional.

137
Q

Planning Game

A

To prioritize work and estimate effort required by creation of a release plan in XP.

138
Q

Planning Poker

A

A tool used to estimate team effort on user stories.

139
Q

PMBOK Guide

A

A Guide to the Project Management Body of Knowledge

140
Q

PMI

A

Project Management Institute

141
Q

Positive Value

A

To maximize value through incremental work in order to gain competitive advantage.

142
Q

Pre-Mortem

A

Team members asked to define reasons of a project’s failure and to identify causes of failure missed in previous analyses.

143
Q

Present Value

A

A way to calculate the time value of money.

144
Q

Process Tailoring

A

To perfect agile processes for a particular project and environment.

145
Q

Productivity

A

The effectiveness of production, usually measured with output per unit of input.

146
Q

Productivity Variation

A

The difference between the planned and actual performance.

147
Q

Product Backlog

A

The known features for a project.

148
Q

Product Road Map

A

An artifact that displays planned project functionality.

149
Q

Product Vision

A

A document that describes what the product is, who will use the product, why the product will be used, and how the product supports the strategy of a company.

150
Q

Product Vision Statement

A

A statement that defines the purpose and value of the product.

151
Q

Programmer

A

The role of a team member that writes the code, a role used in XP.

152
Q

Progressive Elaboration

A

An approach for planning that occurs in cycles instead of upfront, which happens frequently.

153
Q

Project

A

An enterprise planned and designed to create a product, service, or result.

154
Q

PMP

A

Project Management Professional credential.

155
Q

Prototyping

A

A model used to perfect requirements.

156
Q
A

PMI-ACP (3 decks)

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