PSPO-i Flashcards

1
Q

��”

A

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

A

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

A

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

A

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

A

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

A

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

A

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

A

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

A

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

A

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

A

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

A

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q
A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
"Product Backlog refinement"
"the activity in a Sprint through which the Product Owner and the Developers add granularity to the Product Backlog"
26
27
"Product Owner"
"Role in Scrum accountable for maximizing the value of a product, primarily by incrementally managing and expressing business and functional expectations for a product to the Developers"
28
29
"Product Goal"
"The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define  what will fulfill the Product Goal"
30
31
"Ready"
"a shared understanding by the Product Owner and the Developers regarding the preferred level of description of Product Backlog items introduced at Sprint Planning"
32
33
"Refinement"
"the activity in a Sprint through which the Product Owner and the Developers add granularity to the Product Backlog"
34
35
"Scrum"
"Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems as defined in the Scrum GuideTM"
36
37
"Scrum Board"
"a physical board to visualize information for and by the Scrum Team, often used to manage Sprint Backlog. Scrum boards are an optional implementation within Scrum to make information visible"
38
39
"Scrum Guide"
"the definition of Scrum, written and provided by Ken Schwaber and Jeff Sutherland, co creators of Scrum. This definition consists of Scrum s accountabilities, events, artifacts, and the rules that bind them together."
40
41
"Scrum Master"
"a self managing team consisting of one Scrum Master, one Product Owner, and Developers"
42
43
"Scrum Team"
"a self managing team consisting of one Scrum Master, one Product Owner, and Developers"
44
45
"Scrum Values"
"a set of fundamental values and qualities underpinning the Scrum framework; commitment, focus, openness, respect and courage"
46
47
"Self managing"
"Scrum Teams are cross functional, meaning the members have all the skills necessary to create value each Sprint. They are also self managing, meaning they internally decide who does what, when, and how"
48
49
"Sprint"
"Scrum Event that is time boxed to one month or less, that serves as a container for the other Scrum events and activities. Sprints are done consecutively, without intermediate gaps"
50
51
"Sprint Backlog"
"Scrum Artifact that provides an overview of the development work to realize a Sprint s goal, typically a forecast of functionality and the work needed to deliver that functionality. Managed by the Developers"
52
53
"Sprint Goal"
"a short expression of the purpose of a Sprint, often a business problem that is addressed. Functionality might be adjusted during the Sprint in order to achieve the Sprint Goal"
54
55
"Sprint Planning"
"Scrum Event that is time boxed to 8 hours, or less, to start a Sprint. It serves for the Scrum Team to inspect the work from the Product Backlog that s most valuable to be done next and design that work into Sprint backlog"
56
57
"Sprint Retrospective"
"Scrum Event that is set to a time box of 3 hours, or less, to end a Sprint. It serves for the Scrum Team to inspect the past Sprint and plan for improvements to be enacted during future Sprints"
58
59
"Sprint Review"
"Scrum Event that is set to a time boxed of 4 hours, or less, to conclude the development work of a Sprint. It serves for the Scrum Team and the stakeholders to inspect the Increment of product resulting from the Sprint, assess the impact of the work performed on overall progress toward the Product Goal and update the Product backlog in order to maximize the value of the next period"
60
61
"Stakeholder"
"a person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery. Represented by the Product Owner and actively engaged with the Scrum Team at Sprint Review"
62
63
"Technical Debt"
"the typically unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the total cost of ownership. May exist unintentionally in the Increment or introduced purposefully to realize value earlier."
64
65
"Values"
"When the values of commitment, courage, focus, openness and respect are embodied and lived by the Scrum Team, the *Scrum pillars* of transparency, inspection, and adaptation *come to life* and *build trust* for everyone. The Scrum Team members learn and explore those values as they work with the Scrum events, roles and artifacts"
66
67
"Velocity"
"an optional, but often used, indication of the amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Developers for use within the Scrum Team"
68
69