Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

AGILE PMI DEF > Cards > Flashcards

Cards Flashcards

(115 cards)

Start Studying
1
Q

Accountability

A

“Buck stops here” position for any task or activity – who is ultimately going to be held accountable for something

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

ACT

A

Acronym for Agile Champions Team – a team that evangelizes Agile across the organization

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

ADAPT

A

Acronym for Awareness, Desire, Ability, Promotion, Transfer: A model that describes necessary conditions for success of Agile adoption

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

All-In pattern

A

A pattern for agile adoption wherein the entire organization goes in for agile adoption all at the same time (as opposed to Small pilot – see below)

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

Analysts

A

Usually meant to refer to business analysts who translate business requirements into system requirements

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

Anti-pattern

A

A symptom of a deeper dysfunction that indicates improper or incorrect implementation

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

Architect

A

Usually meant to refer to Technical architects, who establish the design patterns and provide the technology roadmap to the team

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

Assessments

A

Questionnaires or evaluation methods to ascertain the level of maturity in a certain discipline – e.g. Agile assessment

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

ATDD

A

Acceptance Test Driven Development – a pattern of working that emphasizes writing the acceptance tests before even writing the code

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

Backlog

A

A collection of “work items” that the team can work on, resulting in additional value to the team

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

Balanced scorecards

A

A system of measuring the health of a system from various points of view to get a holistic view

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

Big room

A

A pattern for running sprint planning meetings for multiple scrum teams working on the same project

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

Card (or story card)

A

Representing an index card (usually 3X5 inches or 4X6 inches) on which a story is written

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

CDE

A

Acronym for Containers, Differences and Exchanges – constraints within which a self-organized team operates

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

C-FORC

A

Acronym for Commitment, Focus, Openness, Respect, Courage – the values of Scrum

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

Chief Product Owner

A

A title often given to the manager of all the product owners working on a single (large or enterprise scale) product

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

Coach

A

Analogous to a sports trainer or coach – usually indicating a team’s mentor either on a technology or a process

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

Collective ownership

A

The notion that the whole team is collectively responsible and accountable for the success or failure

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

Commitment

A

The team “signing up” to deliver to a certain plan – either a sprint or a release plan

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

Commitment driven planning

A

A method of planning that you can only add as many work items to a sprint or a release as the team is willing to make a commitment towards

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

Communities of practice

A

A collection (usually informal) of team members who share a specific skill or practice (e.g. automation testers)

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

Compliance

A

Demonstrate adherence (usually mandatory) to a certain standard or framework (e.g. ISO 9000)

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

Conditions of satisfaction

A

Usually intended to mean acceptance tests or criteria that will be used to ascertain whether a certain requirement is met

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

Continuous integration

A

An extreme programming practice that believes the code should be always integrated and maintained in usable condition (used in conjunction with automated testing)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Cross-functional teams
A team containing diversity of skills that enables it to deliver a finished increment of product; adding tangible value on its own
26
Daily Standup; Daily Scrum
Term used to describe a daily meeting of the Scrum team
27
Dependencies
A requirement or condition that needs to be fulfilled before something can happen
28
Diehards
Opponents of Scrum who are too much in love with the current methodology
29
Distributed teams
Teams that are geographically dispersed (opposite of collocated)
30
Epic
A large or aggregated user story that captures a major requirement or theme for a project
31
Estimate
Forecast or educated guess about the effort or time required to accomplish some work
32
ETC
Acronym for Enterprise Transition Community (or Committee) – a team that manages and steers an organization’s agile transformation
33
FDD
Acronym for Feature Driven Development - a development methodology founded by Jeff DeLuca
34
Feature Teams
An adaptation of FDD that is used on many methodology that aligns formation of teams along features to be developed
35
Feedback
Informed opinion about some activity or work or process that will help improve it going forward
36
Followers
Passive opponents of the scrum methodology who like to follow the old methods
37
Functional managers
Managers who have reporting authority over the team members, i.e. who own the resources
38
Goal
Description of the end state or where we want to end up
39
Grooming (of backlog)
An activity that involves paying attention to – clarifying, estimating and adding more details (to the user stories in the backlog)
40
Grow and Split
One of the models of expanding Scrum adoption, where the team grows to an extent that it eventually needs to be split into multiple teams
41
Human Resources
Refers to the team members or the department in the organization that is responsible for providing systems and support to the team members
42
Humility
One of the desired attributes of a scrum master; to be able to put the team ahead of self (e.g. let the team take credit for the work)
43
IC
Acronym for Improvement Committees – often formed in an organization’s Scrum transformation to improve a specific area (e.g. Agile Testing)
44
IND
Short for Individualism – one of the parameters for assessing and quantifying cultural differences
45
Integration
Activity of combining the different elements of the system to build the entire system into a deployment ready state
46
Integration Team
A team dedicated to carry out integration activities and overcoming challenges found during integration
47
Iron Triangle
A term sometimes used to describe the Triple constraints on a project, viz. Scope, Cost and Time
48
Kickoff Meeting
A meeting of all the team members and stakeholders at the beginning of a project – to get everybody aligned around the goals of the project
49
Knowledge
One of the attributes necessary for being successful, e.g. as a scrum master – knowing the Scrum methodology
50
Lateral communication
Another way of describing communication that follows informal channels (as in distributed teams)
51
Lateral thinking
Pattern of thinking that is used to encourage diverse and innovative ideas
52
Manual Testing
Testing that is done by hand by a tester
53
Metrics
A measure or indicator that is used to quantify something
54
Multi-tasking
A way of working that requires working on multiple tasks at the same time
55
Organizational gravity
The idea that a new idea will meet some resistance and eventually be weighed down by the inertia of the organization
56
Osmotic communication
Communication that spreads through currents, not just to the direct recipients but those who overhear or are in the cc. list
57
Pair programming
Style of programming where two programmers share a terminal – one drives the coding and the other observes and provides real time feedback
58
Pattern
A recognizable method or formation that gives a more predictable or intended outcome
59
PDI
Acronym for Power-Distance-Index; one of the attributes of quantifying cultural differences
60
Pilot Project
A project that is chosen to test out a new method or process (e.g. pilot project for Scrum adoption)
61
PMO
Acronym for Project Management Office – a committee that maintains the project management processes, templates and guidelines in an organization
62
Potentially Shippable
System that is ready to be shipped to the customers if required
63
Product Backlog
A collection – usually in priority order - of all the work items related to a product that add value to a customer
64
Productivity
A measure of the amount of output that can be generated by a team or an individual or an organization
65
Product line owner
Usually higher designation than Product owner, somebody who owns the backlog for an entire product line
66
Product Owner
A role in the Scrum methodology that is responsible for creating and maintaining the product backlog, roadmap and provide clarity to the team
67
Public display of agility
A method of adopting Agile where you make it known to all that the team is practicing agile (as opposed to a stealth transition)
68
Quality
Sometimes defined as conformance to requirements and fitness of use. A way to measure the suitability of the product for a certain need
69
Refactoring
Changing the code without changing the functionality or interfaces (usually for better readability or performance or enhancing some non-functional characteristic)
70
Release
A process that results in the creation of an official, supported version of a product
71
Release Backlog
A portion of the product backlog that is targeted to be completed in a given project or release
72
Release Planning
The process of planning the work targeted at a particular release of a product
73
Requirements
A need, usually expressed by an end user or customer that the system needs to fulfill
74
Responsibility
One of the desired attributes of the scrum master – accepting responsibility for the scrum master duties and also about the team’s output
75
Retrospective (or Spring retrospective)
A meeting at the end of a Sprint to determine what is working well and what is not and how the team intends to improve the processes and working methods
76
Review (or Sprint review)
A meeting at the end of the sprint where the team showcases the product they have built and solicit feedback about it
77
Rotating scrum master
A method of appointing scrum master where the scrum master duties are changed every few sprints
78
Saboteurs
Active opponents of Scrum who dislike Scrum and will try their best to sabotage the scrum transformation
79
Scaling (e.g. Scaling Scrum)
Applying a pattern or process to a larger scale
80
Scrum Master
A role in the Scrum methodology who is responsible for helping the team, protecting the team and guiding the team
81
Scrum-of-Scrum
A meeting of representatives of multiple scrum teams working on the same project to coordinate the work of the teams
82
Scrum-of-scrum-of-scrums
A higher level meeting than the scrum-of-scrums for really large teams where there could be a very large number of scrum teams
83
Self-organization
The notion that the team does not need external intervention to organize itself around a product or a project’s work
84
Social loafing
Time wasted as a result of too many people involved in a single team
85
Space (or team space or work space)
The area of the office where the Agile team is located when they are working on the project
86
Specialists
Team members who specialize in a particular area or skill (e.g. user interface development)
87
Split and Seed
A pattern of spreading Scrum across an organization where an existing scrum team is split up and team members are assigned to “seed” scrum adoption in other teams
88
Sprint
A time box (usually 1-4 weeks) wherein the team tries to convert a portion of the backlog into a finished product
89
Sprint backlog
The subset of the product or release backlog that the team commits to delivering in a given sprint
90
Sprint planning
A meeting to determine the work to be done during a given sprint
91
Start small pattern
A pattern of agile transformation that relies on performing small pilots before attempting large scale adoption
92
Stealth transition
A method of carrying out agile transformation where you adopt practices slowly and without a public display so as to escape the limelight or harsh scrutiny too early in the process
93
Sustainable pace
A principle of agile development that the speed of development in an agile team should be such that it can be sustained over a long run
94
Task
An activity that is needed to be done to accomplish a certain piece of work for a user story
95
Task board (or progress chart)
Usually a physical board on which the pending, ongoing and done tasks are displayed
96
TDD
Acronym for Test-driven-development. A practice in extreme programming that advocates first writing the automated tests even before writing the code
97
Team member (or Developer)
A member of a scrum team who is not the scrum master or the product owner
98
Tech Lead
Short for Technical Lead – a senior team member who the senior most or most accomplished programmer
99
Technical Debt
The work that has not been completed on a given story. Example tests that are not run, refactoring that is remaining, etc. It accumulates and eventually has to be repaid with interest, hence the term debt
100
Test
An experiment or inspection performed to validate whether a system is working as expected
101
Testing pyramid
The philosophy that bulk of the tests in a project should be unit tests, followed by system tests and then the UI tests
102
Time-box
Limiting the amount of time available for a particular activity to create focus and urgency
103
Time-to-market
The lead time between the inception of an idea and the release of the product in the market
104
Two pizza team
Theory that the scrum team is should only be as large that you can feed them with two large pizzas
105
UAI
Acronym for Uncertainty Avoidance Index – one of the measures to quantify cultural differences
106
UED
Acronym for User Experience Design – specialized activity that designs how the users experience should be as they interact with the system
107
User interface (or UI) tests
Tests of the system that require the system to be exercised using the “official” or published user interface
108
User story (or story)
A short description of the interaction between the user and the system that will help the user accomplish a certain objective
109
Velocity
The amount of work completed in a given sprint
110
Velocity driven planning
A method of planning that uses the observed (or estimated) velocity of the team to determine how much work can be accomplished in a given time box
111
Vision
A short (usually one line) description of the end state for a product or a project
112
WAR room
A room where the team is collocated, usually to solve a problem or achieve some purpose
113
Waterfall
Traditional method for development, which involves a sequence of steps one following the other
114
Whole team responsibility
The idea that the entire team is responsible for success or failure
115
Working software
A system that is in working condition and can be demonstrated to an end user or customer

AGILE PMI DEF (1 decks)

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