Term Glossary Flashcards
(162 cards)
1
Q
Acceptance Test Driven Development
A
A method used to communicate with business customers, developers, and testers before coding begins.
2
Q
Active Listening
A
to focus on what is being said and provide feedback to communicate understanding
3
Q
Adaptive Leadership
A
A leadership style that helps teams to thrive and overcome challenges throughout a project
4
Q
Affinity estimation
A
A method used to place user stories in a comparable-sized group
5
Q
Agile
A
to develop a goal through periodic experimentation in order to fulfill the needs of a complex decision
6
Q
Agile Adaptation
A
to adapt the project plan continuously through retrospectives in order to maximize value creation during the planning process
7
Q
Agile Coaching
A
To help achieve goals that are person or organizational
8
Q
Agile experimentation
A
to use the empirical process, observation, and spike introduction while executing a project to influence planning
9
Q
Agile manifesto
A
a statement that reflects agile philosophy that includes: individuals and interactions of processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to changes over following a plan
10
Q
Agile Manifesto Principles
A
a document that describes the twelve principles of the agile manifesto
11
Q
Agile Manifesto: Customer Satisfaction
A
satisfy customers through early and continuous delivery of products, to test and receive feedback, to inform customers on progress, and to fulfill the customers value by completing priority requirements.
12
Q
Agile Manifesto: Welcome Changes
A
To allow quick responses to the changes in external environments, and late in development to maximize the customers competitive advantage
13
Q
Agile Manifesto: Frequent Delivery
A
To deliver software frequently to the customer, allowing for a quicker product release, faster provision of value to the customer and a shorter delivery timeframe
14
Q
Agile Manifesto: Collocated Team
A
to have individuals work together daily on a project to implement osmotic communication, focus, and receive instant feedback to achieve a common goal
15
Q
Agile Manifesto: Motivated Individuals
A
to give individuals the empowerment, support, environment, and trust needed to complete a task susccessfully
16
Q
Agile Manifesto: Face to Face communication
A
the most efficient and effective way to communicate in order to receive direct feedback and influence osmotic communication
17
Q
Agile Manifesto: Working Software
A
working software enables the measurement of progress, enhance customer satisfaction, and maintain and improve the quality of the software to help support project goals.
18
Q
Agile Manifesto: Constant Pace
A
To help team members establish a healthy work-life balance, remain productive, and respond to changes swiftly or progress during a project
19
Q
Agile Manifesto: Continuous Attention
A
to enhance agility and time spent on work requirements in order to maintain a well balanced work environment
20
Q
Agile Manifesto: Simplicity
A
Allows team members to focus on what is necessary to achieve the requirements needed to create and deliver value to the project and customer.
21
Q
Agile Manifesto: Self-organization
A
a team that knows how to complete tasks effectively , has dedication to the project, and is expert on the process of the project
22
Q
Agile Manifesto: Regular Reflection
A
This allows a team to learn how to become more effective, what changes need immediate implementation, and behavior that needs adjustment
23
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
24
Q
Agile Methodologies
A
a way to complete a goal effectively and efficiently.
25
Agile Modeling
A workflow depiction of a process or a system a team can review before it is turned in to code. Stakeholders shoulder understand the model.
26
Agile Planning
The most important aspect of the agile project. Planning happens at multiple levels such as strategic, release, iteration, and daily. Planning must happen upfront and can change throughout the project.
27
Agile practices
to make use of the agile principles through activities
28
Agile Smells
symptoms of a problem that effect agile teams and projects
29
Agile Space
a space that allows team members to establish collaboration, communication, transparency, and visibility.
30
Agile themes
Themes used to help the team focus on the functions of the iteration
31
Agile Tooling
To increase team morale through the use of software or artifacts
32
Analysis
To develop possible solutions by studying the problem and its underlying need and to understand the information provided
33
Approved iterations
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.
34
Architectural Spikes
Spikes that relate to any area of a system, technology, or application domain that is unknown
35
Artifact
A process or work output ex: document, code
36
ASD
Exhibits continuous adaptation to the project and its process with characteristics that include: mission focused, feature based, iterative, time-boxed, risk driven, and change tolerant
37
Automated testing tools
These tools allow for efficient and strong testing. Examples: peer review, periodical code reviews, refactoring, unit tests, automatic and manual testing
38
Being Agile
to work in a responsive way to deliver the products or services the customer needs and when they want the products or services.
39
Brainstorming
an effective and efficient way of gathering ideas within a short period of time for a group
40
Burn-down chart
a chart used to display progress during and at the end of an iteration. Burning down means the backlog will lessen throughout the iteration
41
Burn Rate
the rate of resources consumed by the team. also cost per iteration
42
Burn-Up chart
A chart that displayed completed functionality. Progress will trend upward as stories are completed. only shows complete functions, it is not accurate at predicting or showing works in progress
43
CARVER
an acronym to measure the goals and missions of a project with each letter meaning Criticality, Accessibility , Return, Vulnerability, Effect, and Recognizability
44
Ceremony
A meeting conducted during an agile project which consists of daily standup, iteration planning, iteration review, and iteration retrospective
45
Change
to change requirements that increase value to the customer
46
Charter
a document created during the initiation that formally begins the project. the document includes the projects justification, a summary level budget, major milestones, critical success factors, constraints, assumptions, and authorization to do it.
47
Coach
a team role that keeps the team focused on learning the process
48
Collaboration
A method of cooperation among individuals to achieve a common goal
49
Collective code ownership
The entire team is responsible for 100% of the code
50
Collocation
The entire team is physically present working together in one room
51
Common Cause
an issue solved through trend analysis because the issue is systemic
52
Communication
To share smooth and transparent information of needs
53
Command and Control
Decisions created by higher up individuals in the organization and handed over to the team.
54
Compliance
To meet regulations, rules, and standards.
55
Cone of Silence
An environment for the team that is free of distractions and interruptions.
56
Conflict
Disagreements in certain areas between individuals.
57
Conflict Resolution
An agreement made after a conflict.
58
Continuous Improvement
To ensure that self-assessment and process improvement occurs frequently to improve the product.
59
Continuous Integration
To consistently examine a team member’s work. To build, and test the entire system.
60
Coordination
To organize work with the goal of higher productivity and teamwork.
61
Cost Performance Index (CPI)
To measure the cost spent on a project and its efficiency. Earned Value / Actual Cost = CPI
62
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.
63
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.
64
Cumulative Flow Diagram
A chart that displays feature backlog, work-in-progress, and completed features.
65
Customer-Valued Prioritization
To deliver the maximum customer value early in order to win customer loyalty and support.
66
Cycle Time
The time needed to complete a feature (user story).
67
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.
68
Decide As Late As Possible
To postpone decisions to determine possibilities and make the decision when the most amount of knowledge is available.
69
DEEP
The qualities of a product backlog which include: detailed, estimate-able, emergent, and prioritized.
70
Deliverables
A tangible or intangible object delivered to the customer. Ex. Document, Pamphlet, Report
71
Disaggregation
To separate epics or large stories into smaller stories.
72
Dissatisfaction
The lack of satisfaction among workers such as, work conditions, salary, and management-employee relationships. Factors known as demotivators.
73
Distributive Negotiation
To reach a deal through tactics so both parties receive the highest amount of value possible.
74
Done
When work is complete, and meets the following criteria: complies, runs without errors, and passes predefined acceptance and regression tests.
75
Dot Voting
A system of voting where people receive a certain number of dots to vote on the options provided.
76
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.
77
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.
78
Emergent
Stories that grow and change overtime as other stories reach completion in the backlog.
79
Emotional Intelligence
An individual’s skill to lead and relate to other team members.
80
Epic Story
A large story that spans iterations, then disaggregated into smaller stories.
81
Escaped Defects
Defects reported after the delivery by the customer.
82
Expectancy Theory
An individual chooses to behave in a particular way over other behaviors because of the expected results of the chosen behavior.
83
Exploratory Testing
To inquire how software works with the use of test subjects using the software and asking questions about the software.
84
Extreme Persona
A team-manufactured persona that exaggerates to induce requirements a standard persona may miss.
85
eXtreme Programming (XP)
A methodology in Agile with one-week iterations and paired development.
86
Feature-Driven Development (FDD)
A comprehensive model and list of features included in the system before the design work begins.
87
Feature
A group of stories that deliver value to the customers.
88
Feedback
Information or responses towards a product or project used to make improvements.
89
Fibonacci Sequence
A sequence of numbers used in Agile estimating, 0, 1, 2, 3, 5, 8, 13, 20, 40, 100.
90
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.
91
Fishbone Diagram
A root cause diagram.
92
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.
93
Fixed Time Box
Assigned tasks prioritized for completion based on an estimated number of days. Top priorities are usually completed first.
94
Force Field Analysis
To analyze forces that encourages or resists change.
95
Functionality
An action the customer must see and experience from a system, which will add value to the customer.
96
Grooming
To clean up the product backlog by removal of items, disaggregation of items, or estimation of items.
97
Ground Rules
Unwritten rules decided and followed by team members.
98
Herzberg’s Hygiene Theory
A theory that states factors in the workplace create satisfaction and dissatisfaction in relation to the job.
99
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.
100
Ideal Time
The amount of time needed to complete an assignment without distractions or interruptions.
101
Information Radiator
Artifacts used to help maintain transparency of a project status to team members and stakeholders.
102
Information Refrigerator
Information that is not transparent or useful to the team and stakeholders.
103
Innovation Games
Practice used to induce requirements from product, owners, users, and stakeholders.
104
Integrative Negotiation
To reach an agreement collaboratively that creates more value for both parties by a win-win solution.
105
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.
106
Intraspectives
To inspect within, during a meeting with the Agile team to review practices, usually when a problem or issue occurs.
107
Intrinsic Schedule Flaw
Poor estimation that occurs at the beginning of iteration.
108
INVEST
The benefits of good user stories, which include: Independent, Negotiable, Valuable, Estimate-able, Small, and Testable.
109
Iteration H
Iteration used to prepare the launch of software, and to test software.
110
Iteration 0
Iteration to complete tasks before the development work occurs, for technical and architectural spikes and to gather requirements into the backlog.
111
Kaizen
Based on Japanese management philosophy, to continue improvement through small releases.
112
Kanban
A signal used to advance transparency of work-in-progress, a new task can begin once a previous one is complete.
113
Kanban Board
A chart that shows workflow stages to locate work-in-progress.
114
Kano Analysis
An analysis of product development and customer satisfaction based on needs fulfilled/not fulfilled vs. satisfaction/dissatisfaction.
115
Little’s Law
The law that limits work-in-progress efficiently with development of an appropriate cycle time.
116
Low Performing Team
This team has a lack of trust, no accountability, fear of conflict, less commitment, and less attention to details and results.
117
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.
118
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.
119
Minimal Viable Product (MVP)
A product with only the essential features delivered to early adopters to receive feedback.
120
Minimal Marketing Feature (MMF)
The smallest feature of a product that provides value to the end-user.
121
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.
122
NPV
Net Present Value- A value that compares the amount invested today to the present value of future cash receipts from the investment.
123
Osmotic Communication
To communicate by sharing an environment.
124
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.
125
Participatory Decision Models
To have stakeholder’s involvement in decision making with techniques such as a simple vote.
126
Persona
A depiction of the customer of system with applicable details about usage.
127
Pig
A committed individual impacted by the outcome.
128
Plan-Do-Check-Act
Work cycle in smaller, quick iterations than traditional.
129
Planning Game
To prioritize work and estimate effort required by creation of a release plan in XP.
130
Pre-Mortem
Team members asked to define reasons of a project’s failure and to identify causes of failure missed in previous analyses.
131
Present Value
A way to calculate the time value of money.
132
Process Tailoring
To perfect agile processes for a particular project and environment.
133
Productivity Variation
The difference between the planned and actual performance.
134
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.
135
Product Vision Statement
A statement that defines the purpose and value of the product.
136
Progressive Elaboration
An approach for planning that occurs in cycles instead of upfront, which happens frequently.
137
Requirements at a High Level
Requirements are in the form of user stories, and collected at a high level to estimate a budget.
138
Requirements Prioritization Model
A model to rate each feature with the calculation of weighted formula defined by the team.
139
Requirements Review
To review the requirements so they fulfill the needs and priorities of stakeholders.
140
ROI
Return on Investment- The return an organization makes on an investment expressed by a percentage.
141
Risk-Adjusted Backlog
A product backlog adjusted to help balance the risk and value factors of product.
142
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”.
143
Risk Burn Down
A chart that displays risk and success with feature vs. time.
144
Risk Impact
To analyze the consequences of the risk if they occur based on their probability.
145
Risk Severity
How much the risk’s consequences will influence the success or failure of a project. Risk Probability (%) x Risk Impact ($) = Risk Severity
146
Schedule Performance Index
The ratio of earned value to planned value. EV/PV=SPI.
147
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.
148
Self-Organizing Team
Naturally formed teams that interact with minimal management supervision.
149
Servant Leadership
Leaders collaborate with the team and do anything the team does when needed.
150
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.
151
Specification Breakdown
This occurs when requirements for the specification are incomplete or conflicting.
152
Story Map
A prioritization tool that backlogged stories made smaller and organized by user functionality.
153
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.
154
Technical Debt
Technical decisions a team chooses to not implement currently, but must do so or face difficulty in the future.
155
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.
156
Tracker
A role in XP that measures the team’s progress, and communicates the measurements to the team.
157
Trend Analysis
This analysis provides trends that will occur in the future to help control and implement continuous improvement.
158
Two-Way Communication
To allow communication between parties so their concerns and perspectives are given for effective feedback.
159
Usability Testing
An exploratory test which uses a test subject to understand the usability of software.
160
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.
161
Value-Based Prioritization
To allow the PO or customer determine which function to implement first based on the value it delivers.
162
Value-Driven Delivery
To realize the values needed to deliver a project.
