Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Scrum > Scrum Artifacts > Flashcards

Scrum Artifacts Flashcards

(69 cards)

Start Studying
1
Q

Emergent, ordered list of what is needed to
improve the product

A

Product Backlog

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

Single source of work undertaken by the Scrum
Team.

A

Product Backlog

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

PO’s decisions are visible in the content and
ordering of the “…”

A

Product Backlog

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

While the Product Owner may delegate work,
ultimately, Product Owner remains accountable

A

Product Backlog

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

Attributes of PBI often vary with the domain of
work

A

Product Backlog

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

Multiple Scrum Teams working on the same
product should share the same Product Goal,
Product Backlog, and Product Owner

A

Product Backlog

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

Product Backlog items (PBIs) that can be Done
by the Scrum Team within one Sprint are
deemed ready for selection in a Sprint
Planning

A

Product Backlog

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

If a product exists, this (artifact) also exists, so
is never complete & is a living artifact

A

Product Backlog

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

PBIs can be updated at any time by the PO or
at the PO’s discretion (even outside of PBR)

A

Product Backlog

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

May be adapted (if appropriate) anytime, and
Sprint Review presents a “formal” opportunity
to adapt it

A

Product Backlog

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

Writing PBIs as User Stories (not part of
Scrum) is a common technique adopted by
teams new to Scrum. It is not the only way to
write a PBI. Mature teams use the most
appropriate and effective ways to create PBIs
(and this varies from domain to domain)

A

Product Backlog

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

Describes a future state of the product which
can serve as a target for the Scrum Team to
plan against.

A

Product Goal

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

Is in the Product Backlog

A

Product Goal

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

Is the long-term objective for the Scrum Team

A

Product Goal

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

Scrum Team must fulfill (or abandon) one
objective before taking on the next

A

Product Goal

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

Is the act of breaking down and further defining Product
Backlog Items into smaller more precise PBIs

A

product backlog refinement

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

Is an ongoing activity to add details, such as a
description, order, and size

A

product backlog refinement

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

includes developing and
explicitly communicating the Product Goal

A

product backlog refinement

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

includes creating and
clearly communicating Product Backlog items

A

product backlog refinement

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

includes ordering Product Backlog items

A

product backlog refinement

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

Ensures that the Product Backlog is transparent, visible
and understood

A

product backlog refinement

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

ensures that one PBI can reasonably be completed
within the Sprint time-box

A

product backlog refinement

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

Happens in the (current) Sprint to get PBIs ready for
(future) Sprints

A

product backlog refinement

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

PBIs deemed ready for selection in the (future) Sprint
Planning event acquire this degree of transparency after
refining activities

A

product backlog refinement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
The Developers who will be doing the work are responsible for the sizing of PBIs
product backlog refinement
26
General (old Scrum Guide) recommendation – not a rule – usually consumes 10% of the time, may consume more or less time depending on the domain of the product
product backlog refinement
27
The last opportunity to refine PBIs before they are taken up in the current sprint is Sprint Planning Topic Two - What can be Done this Sprint?
product backlog refinement
28
Sprint Planning will be long and boring if this is not done diligently
product backlog refinement
29
During Sprint Planning, the Scrum Team might not have clarity on the most valuable PBIs if this is not done diligently
product backlog refinement
30
If this is not done diligently, PBIs may be too big to be completed within the Sprint and may not deliver value
product backlog refinement
31
This optimizes the value of the work the Scrum Team performs in the next sprint
product backlog refinement
32
PO may delegate all PBR activities (like writing PBIs, ordering PBIs, etc.) to others, however the PO remains accountable
product backlog refinement
33
Is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable
34
Is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how)
sprint backlog
35
The plan (in Sprint Backlog) by and for the Developers
sprint backlog
36
a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal
sprint backlog
37
created initially in during Sprint Planning
sprint backlog
38
updated throughout the Sprint as more is learned (about what work needs to be done to achieve the Sprint Goal)
sprint backlog
39
The most impactful improvements (from retrospective) *may* be added to the "..." for the next Sprint
sprint backlog
40
During the Sprint, scope of work may be clarified and re-negotiated between the PO & Developers may be reflected here
sprint backlog
41
Is the single objective for the Sprint
sprint goal
42
Provides flexibility (to Developers) in terms of the exact work needed to achieve it
sprint goal
43
creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives
sprint goal
44
Created during Sprint Planning and must be finalized prior to the end of Sprint Planning
sprint goal
45
Does not change during the Sprint
sprint goal
46
As the Developers work during the Sprint, they keep this in mind
sprint goal
47
The purpose of the Daily Scrum is to inspect progress towards this and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work
sprint goal
48
A Sprint could be cancelled (by the Product Owner) if this becomes obsolete
sprint goal
49
The moment a Product Backlog item meets the Definition of Done, a "..." is born
Increment
50
Is a concrete stepping stone toward the Product Goal
Increment
51
Each "..." is additive to all prior "..." and thoroughly verified, ensuring that all "..." work together
Increment
52
In order to provide value, the "..." must be usable
Increment
53
Multiple "..." may be created within a Sprint
Increment
54
this may be delivered to stakeholders prior to the end of the Sprint
Increment
55
(The sum of the) "..." created during the Sprint is presented at the Sprint Review thus supporting empiricism
Increment
56
The entire Scrum Team is accountable for creating a valuable, useful "..."every Sprint
Increment
57
Work cannot be considered part of an "..." unless it meets the Definition of Done
Increment
58
If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review
Increment
59
Product Owner’s decisions are visible through the inspectable "..." presented at the Sprint Review
Increment
60
The Scrum Master serves the Scrum Team in several ways, including helping the Scrum Team focus on creating high-value "..." that meet the Definition of Done
Increment
61
formal description of the state of the Increment when it meets the quality measures required for the product
DoD
62
During the Sprint, "..." ensures that quality (of the increment) does not decrease
DoD
63
Creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment
DoD
64
If "..." for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum.
DoD
65
If it is not an organizational standard, the Scrum Team must create a "..." appropriate for the product
DoD
66
The Developers are required to conform to the "..."
DoD
67
If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same "..."
DoD
68
During Sprint Planning (Topic Three: How will the chosen work get done) the Developers plan the work necessary to create an Increment that meets the "..."
DoD
69
During Sprint retrospective, the "..." is inspected by the Scrum Team and adapted (improved) if necessary
DoD

Scrum (3 decks)

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