Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

PMP - HA > 8 - Agile & Hybrid Management Terminology > Flashcards

8 - Agile & Hybrid Management Terminology Flashcards

1
Q

Acceptance Criteria

A

Customer identified functionality written in enough detail to validate product performance.

Objective criteria that determines if the story achieves the value it represents.

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

Acceptance Test

A

Activities that validate that the features perform in accordance with customer defined functionality.

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

Activity

A

The Agile term for TASK.

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

Adaptive PMLC Model
(Project Management Life Cycle)

A

A change-tolerant life cycle model used for projects where the details of the expected result (solution) are incomplete and/or not well-defined and some functionality is incomplete and/or not well-defined.

An example of an adaptive PMLC Model is an APF (Adaptive Project Framework) project.

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

Agile

A

An iterative software development approach, expressed in a variety of methodologies, which embraces incremental delivery, flexiblity, cross-functional and self-organizing teams, direct customer-developer communication and collaboration, and frequent inspection and adaptation.

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

Agile Coach

A

An experienced leader who consistently directs team members to move beyond the performance of Agile practices and adopt Agile thinking.

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

Agile Development
Life Cycle

A

A comprehensive elaboration that includes continuous integration, refactoring, acceptance testing, cross-functional teams, planning poker, burnup charts, information radiators, and burndown charts.

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

Agile Manifesto

A

Declaration of values and principals for Agile development including prioritizing individuals over processes and working software over extensive documentation.

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

Agile Model

A

A barely sufficient representation that is free from error, understandable, unembellished and coherent.

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

Agile Planning

A

The processes and practices that result in flexible and effective management of a project and include a vision and roadmap among other artifacts.

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

Agreement

A

A Scrum term used to describe the agreement between a product owner and the team that includes the definition of done, the acceptance criteria, and any general agreements.

Can be applied to stories, capabilities, sprints, and releases.

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

Artifact

A

Something made by the team for the project, especially something that may be reused.

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

Backlog

A

An evolving list of customer-prioritized stories, tasks, and bugs that have not been completed and are not being worked on during the current iteration.

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

Backlog Item

A

Any story, task, or bug that has not been completed and is not being worked on during the current iteration.

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

Backlog Refinement
(also referred to as Backlog Grooming or Backlog Maintenance)

A

Continuously updating the prioritized product backlog to reflect any changes, including adding new items, removing items that are no longer appropriate, re-prioritizing existing items as necessary, and refining/cleaning user stories to get them ready for planning and execution.

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

Bug

A

A code defect or error.

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

Burndown Chart

A

A graphical representation of the work (represented by story points for a release and hours for an iteration) remaining over time.

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

Burnup Chart

A

A graphical representation of the work that has been completed over time plotted against the total work.

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

Capacity

A

The amount of work that can be completed in a defined time period taking into consideration the need to perform administrative tasks, the need to perform other work, and absence.

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

Change Management

A

A proactive approach to controlling, communicating and responding effectively to fluctuations.

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

Colocation

A

The desirable state of working in close proximity to promote face-to-face communication.

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

Context Model

A

A graphical representation of the system within the overall environment.

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

Continuous Integration

A

The process of assimilating newly developed iterations into the existing system at frequent intervals via an automated and tested build, so that any faults can be quickly determined and corrected.

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

Core Team

A

Group composed of cross-functional team members with varying levels of Agile knowledge; typically comprised of a sponsor, project management, developers, quality assurance personnel, architecture expert, product manager, and business knowledge experts.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Cross-Functional Team
A group whose members collectively provide the skills required to complete the project.
26
Daily Scrum
Team meeting held on a daily basis used to share the daily reality: 1. What have you done since the last daily scrum? 2. What will you do until the next daily scrum? 3. What impediments stand in your way? ...and to adapt to that reality, which usually involves an immediate re-planning meeting and additional meetings (based on the availability of team members, what technical debt was revealed, and other information that impacts today's work).
27
Dashboard
An information radiator that contains graphical representations depicting progress, trends, and identification of potential issues.
28
Data-Flow Diagram (DFD)
Graphical representation depicting the movement of data between processes, objects, and storage within the system.
29
Definition of Done
A Scrum team representing the object criteria used to determine if a story meets internal standards/constraints.
30
Demo
A working version of the product shown to the customer at the end of an iteration to evidence work done and solicit feedback.
31
Development Team
A self-organizing, cross-functional group of individuals who do the work of the project including analysis, design, development, testing, technical communication, and documentation.
32
Distributed Team
A team working on same project whose members are physically located in separate work sites or locations.
33
Elevator Statement
The synopsis of a concept, such as the purpose of a project, which can be expressed in thirty seconds or so.
34
Emotional Intelligence Quotient (EQ)
The capacity to acknowledge and effectively manage feelings in onself and others.
35
Empirical Process Control
The continuous inspection and adaptation of procedures to ensure any variances in output are within acceptable limits.
36
Epic
A large story, usually undeveloped, that needs to be decomposed into smaller stories.
37
Feature
Business functionality comprised of one or more user stories.
38
Fibonacci Sequence
A series of numbers that begins with 0 and 1, and then is expanded by adding the two previous numbers together: 0, 1, 1, 2, 3, 5, 8, 13...
39
Flow
The rate of value delivery to the customer.
40
Impediment
Anything that prevents the team from working efficiently and effectively.
41
Impediment Backlog
An evolving list of impediments that have not been completed and are not being worked on during the current iteration.
42
Increment
Consecutive changes that increase the amount or value of something.
43
**Information Radiator**
A wall in the common workspace that contains highly visible, graphic representations of progress.
44
Inspect and Adapt
The practice of inspecting a solution at pre-determined stages and, based upon the inspection results, making improvements (adaptations).
45
Interdependent Stories
User stories that, considered together, solve a problem.
46
INVEST
An acronym that stands for the rules that define a user stroy. Independent Negotiable Valuable Estimable Small Testable
47
Issue
A disputed or unsettled condition.
48
Issue Log
A project document that tracks elements which cause stakeholder concern or dissension.
49
Iteration Demo
A working version of the product shown to the customer at the end of an iteration to evidence work done and solicit feedback.
50
Kanban
An evloutionary, incremental process improvement method.
51
Kanban System
A pull system that uses virtual signal cards.
52
Kano Analysis
A model for customer satisfaction that categorizes features as - Must Have's Linear (the more, the better) Exciters/Delighters Dissatisfiers
53
Lean
A methodology that emphasizes the elimiation of waste, producing only what is valuable to the customer.
54
Lean-Agile
The blending of complimentary methodologies that emphasize: Inspection and adaptation Elimination of waste Building in Quality Creation of knowledge
55
Lost Iteration
An iteration that does not result in a deliverable.
56
MMF (Minimum Marketable Feature)
The smallest unit of functionality required for the customer to realize value.
57
Model
A representation of potential solutions to a problem or to one or more aspects of a problem.
58
MoSCoW
A model for prioritization that categorizes features as - Must Have Should Have Could Have Won't Have
59
Muda
An unproductive activity.
60
Osmotic Communication
The indirect absorption of information, often by being present, but not participating, during conversations.
61
Pair Programming
An eXtreme programming practice that pairs two programmers at one stations, typically with one programmer coding (driver) and one reviewing (navigator); an excellent cross-training device.
62
Persona
A fictional character, created by the team to portray a user, used as a reference for determining the viability of a product.
63
Physical Prototype
A representation of the actual environment in which the product will function.
64
Planning Poker
A game played with cards representing tasks that uses Delphi, a method where each team member estimates the size of a task and after a series of discussions, the team arrives at a consensus for task size estimation.
65
Product
An assortment of incorporated features, both tangible and intangible, that offer value to a customer.
66
**Product Owner**
The primary business representative who manages the vision and ROI and has the authority to make decisions. Also called - Product Champion Voice of the Customer
67
Product Review
A Scrum term used to describe an end-of-the-sprint meeting where the team reviews work results with the stakeholders and the stakeholders provide feedback to the team.
68
Product Roadmap
The description of how the project will proceed from its current state to the state described in the vision statement.
69
Product Vision
A statement written by the product owner/customer that describes the desired future state expected to be achieved as the result of the project. Used in lieu of the project charter used for traditional projects.
70
Programmer-Coach
A person, typically a senior programmer, who guides the team in applying XP practices.
71
POC (Proof of Concept)
A model built to test a concept. A prototype.
72
RAD (Rapid Application Development)
An iterative software methodology that relies on rapid prototyping to offset minimal planning.
73
RUP (Rational Unified Process)
An iterative development framework that allows teams to customize the development process.
74
Refactoring
Making changes to the source code that will not alter functionality, but will improve readability and reduce complexity in order to improve the maintainability.
75
Regression Testing
Activities run prior to release that comprehensively validate that the system is defect free and to ensure that new code segments have not corrupted the existing code.
76
Relative Estimation
Assessing the size and complexity of a story by comparing it to previously assessed stories.
77
Release
A deployable software package that incorporates several iterations.
78
Release Backlog
The list of user stories, features, and bugs scheduled for the current release.
79
Release Burndown Chart
A graphical representation of the work, represented by story points, remaining in the release.
80
Release Planning
Defining the prioritized and estimated stories from the product backlog that will be developed in the release and determining the date of the release.
81
Release Testing
The process of evaluating the product to determine that it is suitable for use. Typically includes requires passing acceptance, functional and integration tests.
82
Research Spike
A technical investigation used to minimize risk and uncertainty. Sometimes referred to as an analysis task.
83
Retrospective
A meeting held at the end of each iteration in which the team discusses what worked, what didn't and what could be improved.
84
Roadmap
A document that contains the high-level plan of the features that will be developed during the next few releases. The product owner/customer owns and maintains the document.
85
Sandbox
An environment that confines the impact of errors to as few people as possible. Typically divided into - Development Project Integration Demo QA Production
86
Scrum
An Agile methodology that delivers finished increments of a product at the end of each Spring (a timeboxed iteration with a duration of 1-4 weeks).
87
ScrumMaster
The servant leader and facilitator who ensures that the Scrum process is followed, that Scrum is used in a positive way by the team, and that the team is continually improving in its use of Scrum.
88
Scrum of Scrums
A planning forum used in multiple-team projects to coordinate resources and dependencies.
89
Scrum Roles
A person's identity within the project such as a product owner, ScrumMaster, or Scrum team.
90
Scrum Team
A self-organizing, cross-functional group of individuals who do the work of the Scrum.
91
Scrum Values
Openness, focus, commitment, courage, visibility and humor.
92
Self-Adapting
Modification of a process as quickly as needed to bring greater efficiency and effectiveness to the project.
93
Self-Organization
A management philosophy that delegates work related decisions to those closest to the work.
94
Servant Leader
A leader whose focus is on providing what the team needs, removing roadblocks, and performing tasks that will support and improve team productivity.
95
Situational Leadership
The adaptation of leadership to the task at hand and in consideration of the maturity of the team.
96
SMART Goals Activity
Objects that are: Specific Measureable Attainable Relevant Timely
97
Spike
A short, timeboxed research effort that is necessary to estimate the size of a specific story, usually a technical story.
98
**Sprint Backlog**
The list of stories scheduled for the current iteration.
99
Sprint Planning
A meeting between the product owner and the team to prioritize and identify stories for the next Sprint.
100
Sprint Retrospective Meeting
A meeting held at the end of each Sprint in which the ScrumMaster and the team discuss what went well and what could be improved during the next Spring. Part of the inspect and adapt philosophy.
101
Sprint Review
An informal meeting at the end of the Sprint to demonstrate to the product owner what was accomplished during the Spring.
102
Sprint Task
A manageable unit of work decomposed from a story and estimated in hours.
103
Sprint Team
A self-organizing, cross-functional team that includes the product owner, developers and testers.
104
Story
A document describing a unit of functionality written is business language that is used as the basis of conversation between the product owner and the team to elicit functionality details.
105
Story Board
A Scrum term used to describe a team tool that lists the sprint tasks ordered by story.
106
Story Point
A measurement that defines the size and complexity of a story/user story relative to a previously estimated story/user story.
107
Subject Matter Expert
Any person who has deep, specialized knowledge of a subject.
108
Swarm
The assignment of all capable team members to a specific task with a high priority.
109
Task
A decomposed portion of a story/user story.
110
Task Board
A surface upon which tasks written on cards are grouped under their user stories and pinned in priority order. Used to track the progress of a project.
111
Task List
The list of tasks assigned to the current iteration.
112
Team Dynamics
The manner in which team members interact with each other.
113
Team War Room
The area where the team works, customer meetings take place, and, to promote transparency, a visual representation of project activities, data, and ideas are accesible to everyone in the room.
114
Team Work Agreement
A document created by the team, and facilitated by the project manager, that lists 10-15 commitments that relate to team work, e.g., the work isnt' done until it meets our definition of done.
115
Team-Building
Activities or exercises that promote molding a group of individuals into a team.
116
Technical Debt
An obligation incurred as a result of an opportunistic design or architectural approach which results in complexity and increased costs in the long term. Can also refer to code that will be difficult to maintain as a result of ignoring the definition of done, writing poor code, or writing poor tests.
117
Test Case
The set of conditions or variables used to evaluate the completion status and acceptability of work.
118
TDD (Test-Driven Development)
A methodology, reliant on short developmental cycles, where code validation is written before the code is written.
119
Tester
The person responsible for validating and verifying that the product is done and is acceptable.
120
Timeboxing
Allotting a fixed period of time to an activity.
121
Unit Test
Activities that validate the smallest testable parts of the system.
122
Use Case
A document that defines how the user will interact with the product and how the product will respond to the user.
123
UAT (User Acceptance Test)
Activities that validate that the product behaves in accordance with the user stories.
124
User Roles
An aggregation of attributes that characterize a group of users.
125
User Story
A document describing a unit of functionality written in business language that is used as the basis of conversation between the product owner/customer and the team to elicit functionality details. A user story is - 1. Independent 2. Negotiable 3. Valuable 4. Estimable 5. Small 6. Testable
126
Value Stream Mapping
The identification of the process steps to analyze, design, build and deploy a product. Tools are available to execute this process.
127
Value-Added
Extra features that make a product more desirable, but add little or nothign to the cost.
128
Velocity
The rate at which stories are completed during an iteration, typically measured in story points. Also known as Team Velocity.
129
Vision Statement
A document that defines the goal of the project, typically referencing the target customer, the need or opportunity, and the key benefit. Often includes the main alternative to the project and why the project goal is more desirable.
130
Waste
Anything that does not add value for the customer.
131
WIP Constraint
Any limitation to a work in progress.
132
WIP (Work In Progress)
Software that is in the process of development, but has not yet been deployed. Calculated by multiplying throughput (rate at which items pass through the system) by lead time (time between two successive deliveries).
133
Work Product
Artifact created during development that is typically thrown away or converted into a deliverable.

PMP - HA (18 decks)

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