Course 5 Google PMP_Vocab Flashcards

1
Q

Acceptance criteria

A

The checklist the project manager uses to decide whether a story is done

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

Adaptation

A

Adjusting project, product, or processes to minimize any further deviation or issues

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

Agile Manifesto

A

A collection of four values and 12 principles that define the mindset that all Agile teams should strive for

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

Agile project management

A

An approach to project and team management that embodies “agility” based on the Agile Manifesto

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

Ambiguity

A

A state where conditions and root causes of events or circumstances are unclear, leading to the possibility of misunderstanding

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

Backlog refinement

A

The act of keeping the Backlog prioritized, estimated, and described so the Scrum Team can operate effectively

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

Burndown chart

A

A visual that measures time against the amount of work done and amount of work remaining

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

Business agility

A

Refers to incorporating Agile principles into the wide sphere of management

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

Business collaboration

A

The concept that collaborating with customers gets critical business information to the team immediately, allowing them to adjust and adapt new information instantly

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

Capacity

A

The amount of work a team can handle in a given amount of time

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

Case studies

A

In-depth, data-driven analyses of a business, community, or organization

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

Change control board

A

A formal and rigorous process to manage any changes to requirements

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

Change management

A

The process of getting people to adopt a new product, process, or value system

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

Coaching

A

A two-way communication style aimed at influencing and developing employees’ skills, motivation, and judgment

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

Complexity

A

Refers to the high number of interrelated forces, issues, organizations, and factors that would influence a project

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

Continuous integration and continuous refactoring

A

The Extreme Programming practice of merging product changes into a shared version several times a day in order to get quick feedback on the quality of the code or product

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

CSV file

A

A file type that holds a spreadsheet’s data

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

Cynefin framework

A

A framework used for measuring project complexity

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

Daily Scrum

A

A brief meeting of up to 15 minutes that takes place every day of the Sprint to inspect progress toward the goal

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

Definition of Done

A

An agreed-upon set of items that must be completed before a project or user story can be considered complete

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

Deliverable

A

A tangible outcome from a project

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

Development Team

A

In Scrum, the people who do the work to build the product

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

DevOps

A

An organizational and cultural movement that aims to increase software delivery velocity, improve service reliability, and build shared ownership among software stakeholders

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

Disciplined Agile Delivery (DAD)

A

A hybrid approach that combines the strategies from various Agile frameworks, including Kanban, LeSS, Lean Development, Extreme Programming, and Agile Modeling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Empiricism
The idea that true knowledge comes from actual, lived experience
26
Epic
A group or collection of user stories
27
Extreme Programming (XP)
A methodology that aims to improve product quality and the ability to respond to changing customer needs
28
Five values of Scrum
The core values that guide how Scrum Teams work and behave
29
Flow
A core principle of Kanban that aims to maximize efficiency
30
I.N.V.E.S.T
Acronym for the criteria each user story should meet
31
Incremental
Describes work that is divided into smaller chunks that build on one another
32
Influencer
Someone who is able to lead and influence others to change their behaviors, hearts, and minds to produce meaningful, sustainable results
33
Inspection
A timely check toward the outcome of a Sprint Goal to detect undesirable variances
34
Iterative
Refers to repeating cycles of delivery
35
Kanban
A methodology that provides visual feedback to everyone who might be interested in the status of the work in progress
36
Large-Scale Scrum (LeSS)
A framework that aims to maximize the Scrum Team’s ability to deliver value and reduce waste in larger organizations
37
Lean
A methodology in which the main principle is the removal of waste within an operation
38
Managing
The act of overseeing the work of others
39
Minimum viable product (MVP)
A version of a product with just enough features to satisfy early customers
40
Mission
A short statement that stays constant for the team throughout the project and gives them something to work toward
41
Organizational culture
Describes shared workplace values and shows up in people’s behaviors, activities, the way they communicate, and how they work with each other
42
Pair Programming
The XP practice that refers to when two team members work together at the same time on one task
43
Product Backlog
The single authoritative source for things a team works on
44
Product Goal
The desired future state of the product
45
Product increment
What is produced after a given Sprint
46
Product Owner
In Scrum, the role responsible for maximizing the value of the product and the work of the team
47
Product requirements document
A document that lists the scope and requirements of the project
48
Product roadmap
A visualization or document that provides a high-level view of the expected product, its requirements, and an estimated schedule for reaching milestones
49
Product vision
Defines what the product is, how it supports the customer’s business strategy, and who will use it
50
Relative estimation
A comparison of the effort for a task to the effort for another task
51
Releasable
Refers to when the team has developed a minimum viable product of a given feature or requirement
52
Release plans
Indicates the approximate date when the team is expected to release and deliver certain features to the customer or user
53
Requirements
Conditions that must be met or tasks that must be finished to ensure the successful completion of the project
54
Retrospectives and continuous learning
Refers to striving continuously to learn and adapt to what’s working and what’s not
55
Scaled Agile Framework (SAFe)
A Lean-Agile scaling framework that combines concepts from Kanban, Scrum, Extreme Programming (XP), DevOps, and Design Thinking methodologies
56
Scrum
A framework for developing, delivering, and sustaining complex products
57
Scrum Master
In Scrum, the role responsible for ensuring the team lives Agile values and principles and follows the processes and practices the team agreed to
58
Scrum of Scrums
A technique for integrating the work of multiple, smaller Scrum Teams working on the same project or solution
59
Solution Design Sprint
An entire Sprint spent working solely on the solution design
60
Spotify model
The Spotify organization’s version of the Agile approach
61
Sprint
A timeboxed iteration where a planned amount of work is done
62
Sprint Backlog
The set of Product Backlog items that are selected to be completed during the upcoming Sprint
63
Sprint Planning
Refers to when the entire Scrum Team comes together to map out what will be done during the Sprint
64
Sprint Retrospective
An essential meeting of up to three hours for the Scrum Team to take a step back, reflect, and identify improvements about how to work together as a team
65
Sprint Review
A meeting with the entire Scrum Team where the product is demonstrated to determine which aspects are finished and which aren’t
66
Stacey Matrix
A framework developed to help project managers identify the complexities of their environment so they can adapt their style of decision-making
67
Story points
A method for estimating user stories, tasks, and backlog items by assigning a point value based on effort and risk
68
T-shirt sizes
A way to estimate what is needed for a work effort in terms of time, budget, and energy by categorizing it as XS, S, M, L, XL, or XXL
69
Team dynamics and culture
Refers to creating an effective team culture that is inclusive, supportive, and empowering
70
Three pillars of Scrum
The foundational concepts on which Scrum is based
71
Timebox
A Scrum concept that refers to the estimated duration for an event
72
Transparency
Making the most significant aspects of the work visible to those responsible for the outcome
73
Uncertainty
A lack of predictability or high potential for surprise
74
User story
A short, simple description of a feature told from the perspective of the user
75
Value delivery
Refers to delivering the work as quickly as possible to get feedback and mitigate time risk
76
Value roadmap
An Agile way of mapping out the timelines and requirements for the product-development process
77
Velocity
A measure of the amount of work a team can take on during a single Sprint
78
Volatility
The rate of change and churn in a business or situation
79
VUCA
The conditions that affect organizations in a changing and complex world
80
Waterfall project management
A project management methodology that refers to the sequential or linear ordering of phases
81
Work-in-progress (WIP) limit
A constraint on how many work items are actively being worked on at any given time