Agile terms Flashcards
1
Q
ACP
A
Agile Certified Practitioner
2
Q
Acceptance Test Driven Development
A
A method used to communicate with business customers, developers, and testers before coding begins
3
Q
Active Listening
A
To focus on what is said and provide feedback to communicate understanding
4
Q
Adaptive Leadership
A
A leadership style that helps teams to thrive and overcome challenges throughout a project
5
Q
Affinity Estimation
A
A method used to quickly place user stories into a comparable-sized group.
6
Q
Agile
A
To develop a goal through periodic experimentation in order to fulfil the need of a complex decision
7
Q
Agile Adaptation
A
To adapt the project plan continuously through retrospectives in order to maximize value creation
during the planning process
8
Q
Agile Coaching
A
To help achieve goals that is either personal or organizational
9
Q
Agile Experimentation
A
To use the empirical process, observation, and spike introduction while executing a project to influence
planning
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
11
Q
Agile Methodologies
A
A way to complete a goal effectively and efficiently. Examples of Agile Methodologies include XP, Scrum,
and Lean
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
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
14
Q
Agile Practices
A
To make use of the Agile principles through activities
15
Q
Agile Projects
A
A project that occurs based on the Agile Manifesto and Agile Principles
16
Q
Agile Smells
A
Symptoms of problems that affect Agile teams and projects
17
Q
Agile Space
A
A space that allows team members to establish collaboration, communication, transparency, and
visibility
18
Q
Agile Themes
A
Themes used to help the team focus on the functions of iteration
19
Q
Agile Tooling
A
To increase team morale with software or artifacts
20
Q
Analysis
A
To develop possible solutions by studying the problem and its underlying need and to understand the
information provided
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
22
Q
Architectural Spikes
A
Spikes that relate to any area of a system, technology, or application domain that is unknown
23
Q
Artifact
A
A process or work output Ex. Document, Code
24
Q
ASD
A
Adaptive Software Development 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
25
Automated Testing Tools
These tools allow for efficient and strong testing. Examples: Peer Reviews, Periodical Code-Reviews,
Refactoring, Unit Tests, Automatic and Manual Testing
26
Being Agile
To work in a responsive way to deliver the products or services a customer needs and when they want the products or services
27
Brainstorming
An effective and efficient way of gathering ideas within a short period of time from a group
28
Burn-Down Chart
A chart used to display progress during and at the end of iteration. “Burning down” means the backlog will lessen throughout the iteration
29
Burn Rate
The rate of resources consumed by the team; also cost per iteration
30
Burn-Up Chart
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
31
CARVER
An acronym to measure the goals and mission of the project with each letter meaning: Criticality, Accessibility, Return, Vulnerability, Effect, and Recognizeability
32
Ceremony
meeting conducted during an Agile project that consists of daily stand-up, iteration planning, iteration review, and iteration retrospective
33
Change
To change requirements that increase value to the customer
34
Charter
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
35
Chicken
An individual involved but not committed to an Agile project.
36
Coach
A team role that keeps the team focused on learning and the process
37
Collaboration
A method of cooperation among individuals to achieve a common goal
38
Collective Code Ownership
The entire team together is responsible for 100% of the code
39
Collocation
The entire team is physically present, working in one room.
40
Common Cause
An issue solved through trend analysis because the issue is systematic
41
Communication
To share smooth and transparent information of needs
42
Command & Control
Decisions created by higher up individuals in the organization and handed over to the team.
43
Compliance
To meet regulations, rules, and standards
44
Cone of Silence
An environment for the team that is free of distractions and interruptions
45
Conflict
Disagreements in certain areas between individuals
46
Conflict Resolution
An agreement made after a conflict
47
Continuous Improvement
To ensure that self-assessment and process improvement occurs frequently to improve the product
48
Continuous Integration
To consistently examine a team member’s work. To build, and test the entire system
49
Coordination
To organize work with the goal of higher productivity and teamwork
50
Cost Performance Index (CPI)
To measure the cost spent on a project and its efficiency. Earned Value / Actual Cost = CPI
51
Cross-Functional Team
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
52
Crystal Family
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
53
Cumulative Flow Diagram
A chart that displays feature backlog, work-in-progress, and completed features
54
Customer
The end-user who determines and emphasizes business values.
55
Customer-Valued Prioritization
To deliver the maximum customer value early in order to win customer loyalty and support
56
Cycle Time
The time needed to complete a feature (user story).
57
Daily Stand Up
A brief meeting where the team shares the previous day’s achievements, plans to make achievements, obstacles, and how to overcome the obstacles
58
Decide As Late As Possible
To postpone decisions to determine possibilities and make the decision when the most amount of knowledge is available
59
DEEP
The qualities of a product backlog which include: detailed, estimate-able, emergent, and prioritized
60
Deliverables
A tangible or intangible object delivered to the customer. Ex. Document, Pamphlet, Report
61
Disaggregation
To separate epics or large stories into smaller stories
62
Dissatisfaction
The lack of satisfaction among workers such as, work conditions, salary, and management-employee relationships. Factors known as demotivators
63
Distributive Negotiation
To reach a deal through tactics so both parties receive the highest amount of value possible.
64
Done
When work is complete, and meets the following criteria: complies, runs without errors, and passes predefined acceptance and regression tests
65
Dot Voting
A system of voting where people receive a certain number of dots to vote on the options provided
66
Dynamic Systems Development Model (DSDM)
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
Earned Value Management (EVM)
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
Emergent
Stories that grow and change overtime as other stories reach completion in the backlog
69
Emotional Intelligence
An individual’s skill to lead and relate to other team members
70
Epic Story
A large story that spans iterations, then disaggregated into smaller stories
71
Escaped Defects
Defects reported after the delivery by the customer
72
Expectancy Theory
An individual chooses to behave in a particular way over other behaviors because of the expected results of the chosen behavior
73
Exploratory Testing
To inquire how software works with the use of test subjects using the software and asking questions about the software
74
Extreme Persona
A team-manufactured persona that exaggerates to induce requirements a standard persona may miss.
75
eXtreme Programming (XP)
A methodology in Agile with one-week iterations and paired development
76
Feature-Driven Development (FDD)
A comprehensive model and list of features included in the system before the design work begins
77
Feature
A group of stories that deliver value to the customers
78
Feedback
Information or responses towards a product or project used to make improvements
79
Fibonacci Sequence
A sequence of numbers used in Agile estimating, 0, 1, 2, 3, 5, 8, 13, 20, 40, 100.
80
Finish Tasks One by One
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
Fishbone Diagram
A root cause diagram
82
Five Whys
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
Fixed Time Box
Assigned tasks prioritized for completion based on an estimated number of days. Top priorities are usually completed first
84
Focus
To stay on task, and is facilitated by the scrum master or coach
85
Force Field Analysis
To analyze forces that encourages or resists change
86
Functionality
An action the customer must see and experience from a system, which will add value to the customer
87
Grooming
To clean up the product backlog by removal of items, disaggregation of items, or estimation of items
88
Ground Rules
Unwritten rules decided and followed by team members
89
Herzberg’s Hygien
A theory that states factors in the workplace create satisfaction and dissatisfaction in relation to the job
90
High-Bandwidth Communicati
Face-to-face communication that also includes non-verbal communication
91
High Performing Team
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
Ideal Time
The amount of time needed to complete an assignment without distractions or interruptions.
93
Incremental Delivery
Functionality conveyed in small phases
94
Incremental Project Releases
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
Information Radiator
Artifacts used to help maintain transparency of a project status to team members and stakeholders
96
Information Refrigerator
Information that is not transparent or useful to the team and stakeholders
97
Innovation Games
Practice used to induce requirements from product, owners, users, and stakeholders
98
Integrative Negotiation
To reach an agreement collaboratively that creates more value for both parties by a win-win solution.
99
Interaction
Face-to-Face communication
100
IRR
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
Intraspectives
To inspect within, during a meeting with the Agile team to review practices, usually when a problem or issue occurs.
102
Intrinsic Schedule Flaw
Poor estimation that occurs at the beginning of iteration.
103
INVEST
The benefits of good user stories, which include: Independent, Negotiable, Valuable, Estimate-able, Small, and Testable
104
Iteration
Work cycle, Scrum uses 2-4 weeks, XP uses 1 week
105
Iteration Backlog
Work to complete in a particular iteration
106
Iteration H
Iteration used to prepare the launch of software, and to test software.
107
Iteration 0
Iteration to complete tasks before the development work occurs, for technical and architectural spikes and to gather requirements into the backlog.
108
Iteration Retrospective
A meeting used in Scrum, the team discusses ways to improve after work is completed.
109
Just-In-Time
Used to minimize inventory cost by materials delivered before they are required
110
Kaizen
Based on Japanese management philosophy, to continue improvement through small releases
111
Kanban
A signal used to advance transparency of work-in-progress, a new task can begin once a previous one is complete
112
Kanban Board
A chart that shows workflow stages to locate work-in-progress
113
Kano Analysis
An analysis of product development and customer satisfaction based on needs fulfilled/not fulfilled vs. satisfaction/dissatisfaction
114
Last Responsible Moment
To make decisions as late as possible in order to preserve all possible options
115
Lean Methodology
To eliminate waste, an Agile method derived from manufacturing.
116
Little’s Law
The law that limits work-in-progress efficiently with development of an appropriate cycle time
117
Low Performing Team
This team has a lack of trust, no accountability, fear of conflict, less commitment, and less attention to details and results
118
Lean Software Development (LSD)
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
Maslow’s Hierarchy of Needs
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
Metaphor
To explain how a project will be completed successfully to stakeholders by use of real-world examples of systems and components
121
Minimal Viable Product (MVP)
A product with only the essential features delivered to early adopters to receive feedback.
122
Minimal Marketing Feature (MMF
The smallest feature of a product that provides value to the end-user.
123
Monopoly Money
To give fake money to business features in order to compare the relative priority of those features
124
MoSCoW Analysis
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
Negotiation
To reach an agreement between two or more parties to resolve a conflict
126
Negotiable
Anything opened to discussion
127
NPV
Net Present Value- A value that compares the amount invested today to the present value of future cash receipts from the investment
128
Osmotic Communication
To communicate by sharing an environment
129
Pair Programming
When developers work together in XP Practice
130
Pareto Principle
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
Parking Lot
A storage place for ideas that distract from the main goal during a meeting
132
Participatory Decision Models
To have stakeholder’s involvement in decision making with techniques such as a simple vote
133
Persona
A depiction of the customer of system with applicable details about usage.
134
Personnel Loss
When an employer faces the loss of a human resource through death, injury, or disability of an employee.
135
Pig
A committed individual impacted by the outcome
136
Plan-Do-Check-Act
Work cycle in smaller, quick iterations than traditional
137
Planning Game
To prioritize work and estimate effort required by creation of a release plan in XP.
138
Planning Poker
A tool used to estimate team effort on user stories.
139
PMBOK Guide
A Guide to the Project Management Body of Knowledge
140
Positive Value
To maximize value through incremental work in order to gain competitive advantage.
141
Pre-Mortem
Team members asked to define reasons of a project’s failure and to identify causes of failure missed in previous analyses.
142
Present Value
A way to calculate the time value of money
143
Process Tailoring
To perfect agile processes for a particular project and environment.
144
Productivity
The effectiveness of production, usually measured with output per unit of input.
145
Productivity Variation
The difference between the planned and actual performance
146
Product Backlog
The known features for a project.
147
Product Road Map
An artifact that displays planned project functionality
148
Product Vision
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.
149
Product Vision Statement
A statement that defines the purpose and value of the product
150
Programmer
The role of a team member that writes the code, a role used in XP.
151
Progressive Elaboration
An approach for planning that occurs in cycles instead of upfront, which happens frequently.
152
Project
An enterprise planned and designed to create a product, service, or result
153
Prototyping
A model used to perfect requirements
154
Qualitative
Descriptive data used for analysis
155
Quality
The specifications and requirements of product or service measured against the standard product or service in the industry
156
Quantitative
Numerical data used for analysis.
157
Refactoring
To adjust working code to improve functionality and conservation.
158
Relative Prioritization
A list of all user stories and features ordered by highest priority to the lowest priority
159
Relative Sizing
To estimate the size of a story in comparison with another story.
160
Release
Iteration outcomes delivered to customers (end-users).
161
Release Plan
A document that describes the timeline of a product release
162
Requirements at a High Level
Requirements are in the form of user stories, and collected at a high level to estimate a budget.
163
Requirements Prioritization Model
A model to rate each feature with the calculation of weighted formula defined by the team.
164
Requirements Review
To review the requirements so they fulfill the needs and priorities of stakeholders
165
ROI
Return on Investment- The return an organization makes on an investment expressed by a percentage.
166
Risk
The uncertainty of an unwanted outcome related to the project
167
Risk-Adjusted Backlog
A product backlog adjusted to help balance the risk and value factors of product
168
Risk-Based Spike
This spike helps the team remove major risks, and if the spike fails every approach possible, the project is defined as “fast failure”.
169
Risk Burn Down
A chart that displays risk and success with feature vs. time.
170
Risk Impact
To analyze the consequences of the risk if they occur based on their probability.
171
Risk Probability
The likelihood that the risk will occur.
172
Risk Severity
How much the risk’s consequences will influence the success or failure of a project. Risk Probability (%) x Risk Impact ($) = Risk Severity
173
Role
A person’s description that includes their function in an Agile project.
174
Rolling Wave Planning
To divide the planning phase into stages
175
Root Cause Analysis
To investigate beyond the symptoms of the problem and to understand the root cause of the problem
176
Root Cause Diagram
A diagram that correlates different factors and the symptom.
177
Satisfaction
The feeling of workers when their needs are fulfilled. Known as motivators
178
Schedule Performance Index
The ratio of earned value to planned value. EV/PV=SPI.
179
Scope Creep
The uncontrolled changes or growth in a project’s scope which goes beyond the initial agreement
180
Software Development Life Cycle (SDLC)
This cycle tends to be long and requires a lot of advanced planning.
181
Self-Directing Team
This team has the capability to make their own decisions, empowerment, mutual accountability, and collective ownership of a project, which leads them to be more productive and efficient.
182
Self-Organizing Team
Naturally formed teams that interact with minimal management supervision.
183
Servant Leadership
Leaders collaborate with the team and do anything the team does when needed.
184
Shu-Ha-Ri Model
Originated in Japan as a way to understand learning and mastery, Shu – obeying the rules, Ha - consciously moving away from the rules, and Ri – consciously finding an individual path
185
Silo
Work that is isolated.
186
Social Media-Based Communication
Communication used conveniently to receive instant feedback, ideas, and requirements from a particular community.
187
Special Cause
A cause that occurs once because of special reasons
188
Specification Breakdown
This occurs when requirements for the specification are incomplete or conflicting.
189
Spike
An experiment that helps a team answer, a particular question and determine future actions.
190
Sprint Plan
A document that explains sprint goals, tasks, and requirements and how the tasks will reach completion.
191
Sprint Retrospective
A team-member meeting that occurs after each sprint to evaluate the product and process to improve efficiency and effectiveness.
192
Sprint Review
A meeting that occurs after each sprint to show the product or process to stakeholders for approval and to receive feedback
193
Stakeholder
An individual with an interest in the outcome
194
Stakeholder Management
To ensure stakeholders remain informed and that the achievement of their needs are met.
195
Standardized Test
A curved test used to measure knowledge and understanding, but constructed so the same test-taker will perform similarly each time.
196
Story Card
An index card that displays the user story.
197
Story Map
A prioritization tool that backlogged stories made smaller and organized by user functionality.
198
Story Point
A unit of measurement to estimate the difficulty of a user story.
199
Sustainability
A maintainable pace of work that is intense yet steady.
200
Swarming
When the team collaborates to focus on a single user story.
201
Swarming
When the team collaborates to focus on a single user story.
202
Tabaka’s Model
A model originated in Japan to describe a team with values that include self-organization, empowered to make decisions, belief in vision and success, a committed team, trust, participatory decision making, consensus-driven, and construction disagreement.
203
Tasks
The smaller jobs to fulfill a user story, usually divided among team members.
204
Team
A group of individuals charged with the responsibility of delivery and value of a project
205
Teamwork
Team members function in a way that is collaborative to complete tasks and reach a common goal, mostly achieved with strong communication.
206
Team Empowerment
A team that is empowered has collaboration, responsibility, and self-sufficiency.
207
Team Formation
Formation happens when a team creates ground rules and processes to build bonds and shared goals.
208
Team Participation
When the team discusses the requirements that will fulfill the customer’s needs.
209
Team Space
An area for team members to collocate, usually a physical location, in some cases a virtual location is created.
210
Team Velocity
The number of story points completed during iteration, and used to determine the planned capacity
211
Technical Debt
Technical decisions a team chooses to not implement currently, but must do so or face difficulty in the future.
212
Test-Driven Development (TDD)
A written acceptance test for a module with the code built to pass the tests in order to ensure correct performance
213
Tester
Explains acceptance test to the customers then consistently measures the product against the test and records results for the team. (XP Role)
214
Theme
A group of stories, iteration, or release’s idea determined by the customer and the team agrees with the idea.
215
Time-boxing
To set a fixed delivery date for a project or release.
216
Tracker
A role in XP that measures the team’s progress, and communicates the measurements to the team.
217
Traditional Management
A top-down approach that consists of long cycles, heavy planning, and minimal customer involvement.
218
Transparency
To show everyone’s involvement and progress to the entire team.
219
Trend Analysis
This analysis provides trends that will occur in the future to help control and implement continuous improvement.
220
Two-Way Communication
To allow communication between parties so their concerns and perspectives are given for effective feedback.
221
Unit Testing
These tests are used for continuous feedback to achieve quality improvement and assurance.
222
Usability Testing
An exploratory test which uses a test subject to understand the usability of software.
223
Users Involvement
The active involvement of users in the development cycle of a project so team members can receive feedback about the user’s requirements.
224
User Story
At least one business requirement that increases the value for the user.
225
Validation
The way to make sure that the product is acceptable to the customer.
226
Value
The worth of a product, project, or service.
227
Value-Based Prioritization
To allow the PO or customer determine which function to implement first based on the value it delivers.
228
Value-Driven Delivery
To realize the values needed to deliver a project
229
Value Stream Mapping
A tool used to analyze a chain of processes with the desired outcome of eliminating waste.
230
Variance
The measurement of how far apart data is from each other.
231
Velocity
The total number of features that a team delivers in iteration
232
Verification
To ensure the product meets requirements and specifications
233
Virtual Team
A geographically distributed group that does not meet physically.
234
Visibility
The team’s work and progress must be transparent to all stakeholders
235
War Room
A space where the team can work and collaborate effectively.
236
Waterfall
Resistant to change that requires heavy planning and sequential, traditional approach.
237
Wide-Band Delphi Estimating
An estimation technique for user stories. The PO presents user stories & discusses challenges. Each story’s estimates plotted, and then the team comes to an agreement on the range of points.
238
WIP Limits
To limit work-in-progress so a team can do the following: maintain focus on completing work, maintaining quality, and delivering value.
239
Wireframe
A lightweight non-functional UI design that shows the customer the vital elements and how they will interact before coding.
240
WIP
Work-In-Progress- Stories that have started, which are displayed in workflows to show progress and what still needs to be completed.
241
Workflow
A series of phases or stages the team has agreed to execute for a project
242
100-Point Method
A method that allows customers to score (total 100 points) different features of a product.
