Scrum Guide Flashcards

(75 cards)

1
Q

What is Scrum?

A

A lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.

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

Who is responsible for ordering the work in Scrum?

A

The Product Owner.

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

What does the Scrum Team do during a Sprint?

A

Turns a selection of the work into an Increment of value.

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

What are the three pillars of Scrum?

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

What is the purpose of transparency in Scrum?

A

To make the emergent process and work visible to those performing and receiving the work.

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

What is the role of inspection in Scrum?

A

To frequently inspect Scrum artifacts and progress toward agreed goals to detect undesirable variances.

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

What is adaptation in the context of Scrum?

A

Adjusting the process or materials as soon as possible if any aspects deviate outside acceptable limits.

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

List the five values that Scrum Team members must embody.

A
  • Commitment
  • Focus
  • Openness
  • Respect
  • Courage
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the fundamental unit of Scrum?

A

A small team of people, known as the Scrum Team.

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

What are the roles within a Scrum Team?

A
  • Scrum Master
  • Product Owner
  • Developers
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is the accountability of Developers in Scrum?

A
  • Creating a plan for the Sprint (Sprint Backlog)
  • Instilling quality by adhering to a Definition of Done
  • Adapting their plan each day toward the Sprint Goal
  • Holding each other accountable as professionals
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is the main responsibility of the Product Owner?

A

Maximizing the value of the product resulting from the work of the Scrum Team.

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

True or False: The Product Owner can be a committee.

A

False.

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

What is the Scrum Master’s role?

A

Establishing Scrum as defined in the Scrum Guide and helping everyone understand Scrum theory and practice.

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

What is the purpose of the Sprint in Scrum?

A

To create consistency and turn ideas into value.

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

How long can a Sprint last?

A

One month or less.

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

What happens during Sprint Planning?

A

The Scrum Team collaboratively lays out the work to be performed for the Sprint.

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

Fill in the blank: The Daily Scrum is a _______ event.

A

15-minute

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

What is the purpose of the Sprint Review?

A

To inspect the outcome of the Sprint and determine future adaptations.

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

What does the Sprint Retrospective focus on?

A

Planning ways to increase quality and effectiveness.

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

What are Scrum artifacts designed to maximize?

A

Transparency of key information.

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

What is the Product Backlog?

A

An emergent, ordered list of what is needed to improve the product.

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

What commitment is associated with the Product Backlog?

A

The Product Goal.

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

What does the Product Goal describe?

A

A future state of the product serving as a target for the Scrum Team to plan against.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
What is Product Backlog refinement?
The act of breaking down and further defining Product Backlog items into smaller, more precise items (thin slice) ## Footnote This is an ongoing activity to add details such as description, order, and size.
26
Who is responsible for sizing the Product Backlog items?
The Developers who will be doing the work ## Footnote The Product Owner may influence the Developers by helping them understand and select trade-offs.
27
What does the Product Goal describe?
A future state of the product which serves as a target for the Scrum Team to plan against ## Footnote The Product Goal is in the Product Backlog.
28
What is a product considered to be?
A vehicle to deliver value with a clear boundary, known stakeholders, and well-defined users or customers ## Footnote A product could be a service, a physical product, or something more abstract. Value, boundary, stakeholders, customers
29
What is the Sprint Backlog composed of?
The Sprint Goal, the set of Product Backlog items selected for the Sprint, and an actionable plan for delivering the Increment ## Footnote The Sprint Backlog is a plan by and for the Developers.
30
What is the purpose of the Sprint Backlog?
To provide a highly visible, real-time picture of the work that Developers plan to accomplish during the Sprint ## Footnote It is updated throughout the Sprint as more is learned.
31
What is the Sprint Goal?
The single objective for the Sprint ## Footnote It is a commitment by the Developers that provides flexibility in terms of the exact work needed to achieve it.
32
When is the Sprint Goal created?
During the Sprint Planning event ## Footnote It is then added to the Sprint Backlog.
33
What is an Increment in Scrum?
A concrete stepping stone toward the Product Goal that is additive to all prior Increments ## Footnote Each Increment must be usable to provide value.
34
How many Increments may be created within a Sprint?
Multiple Increments ## Footnote The sum of the Increments is presented at the Sprint Review.
35
What must work meet to be considered part of an Increment?
The Definition of Done ## Footnote Work cannot be considered part of an Increment unless it meets this definition.
36
What is the Definition of Done?
A formal description of the state of the Increment when it meets the quality measures required for the product ## Footnote It creates transparency by providing a shared understanding of completed work.
37
What happens if a Product Backlog item does not meet the Definition of Done?
It cannot be released or presented at the Sprint Review and returns to the Product Backlog for future consideration ## Footnote The Definition of Done must be followed by all Scrum Teams if it is part of organizational standards.
38
How do Developers handle Definition of Done when multiple teams work together on a product?
They are required to conform to the Definition of Done ## Footnote Multiple Scrum Teams working together on a product must mutually define and comply with the same Definition of Done.
39
What is a Burn-down Chart?
A chart that shows the amount of work remaining in a backlog over time. ## Footnote It plots time on the horizontal axis and work remaining on the vertical axis.
40
What does a Burn-up Chart represent?
A chart that shows the amount of work completed over time. ## Footnote It plots time on the horizontal axis and work completed on the vertical axis.
41
Define Coherence in the context of Product Backlog items.
The quality of the relationship between certain Product Backlog items making them worthy of consideration as a whole.
42
What is Daily Scrum?
A 15-minute time-boxed event for Developers to plan work for the next 24 hours and optimize team collaboration.
43
What is the Definition of Done?
A formal description of the state of the Increment when it meets the quality measures required for the product. Once definition of done is met, the increment is born.
44
Who is considered a Developer in a Scrum Team?
Any member of a Scrum Team committed to creating any aspect of a usable Increment each Sprint.
45
What does Emergence refer to?
The process of new facts or knowledge coming into existence or prominence unexpectedly.
46
Define Empiricism.
The philosophy that all knowledge originates in experience and observations.
47
What are Engineering standards?
A shared set of development and technology standards applied by Developers to create releasable Increments.
48
What is a Forecast (of functionality)?
The selection of items from the Product Backlog deemed feasible for implementation in a Sprint.
49
What is an Increment in Scrum?
The complete and valuable work produced by the Developers during a Sprint.
50
Define Product Backlog.
An ordered list of the work to be done to create, maintain, and sustain a product.
51
What is Product Backlog refinement?
The activity in a Sprint through which the Product Owner and Developers add granularity to the Product Backlog.
52
Who is the Product Owner?
The role in Scrum accountable for maximizing the value of a product.
53
What is the Product Goal?
Describes a future state of the product serving as a target for the Scrum Team to plan against.
54
What does 'Ready' mean in Scrum?
A shared understanding of the preferred level of description of Product Backlog items introduced at Sprint Planning.
55
Define Scrum.
A lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.
56
What is a Scrum Board?
A physical board used to visualize information for the Scrum Team, often for managing Sprint Backlog.
57
What is the Scrum Guide™?
The definition of Scrum, written by Ken Schwaber and Jeff Sutherland.
58
What is the role of the Scrum Master?
Accountable for guiding, coaching, teaching, and assisting a Scrum Team in understanding and using Scrum.
59
What constitutes a Scrum Team?
A self-managing team consisting of one Scrum Master, one Product Owner, and Developers.
60
What are Scrum Values?
Fundamental values underpinning the Scrum framework: commitment, focus, openness, respect, and courage.
61
What does self-managing mean in Scrum?
Teams decide internally who does what, when, and how.
62
Define a Sprint.
A time-boxed event in Scrum that serves as a container for other Scrum events and activities.
63
What is the Sprint Backlog?
An overview of the development work to realize a Sprint’s goal, typically a forecast of functionality.
64
What is the Sprint Goal?
A short expression of the purpose of a Sprint, often addressing a business problem.
65
What is the purpose of Sprint Planning?
To inspect the work from the Product Backlog that’s most valuable to be done next and design it into the Sprint backlog.
66
What is the Sprint Retrospective?
An event to inspect the past Sprint and plan for improvements for future Sprints.
67
What occurs during the Sprint Review?
The Scrum Team and stakeholders inspect the Increment of product and assess the impact of the work performed.
68
Who are Stakeholders in Scrum?
Persons external to the Scrum Team with specific interest and knowledge of a product needed for incremental discovery.
69
What is Technical Debt?
The overhead of maintaining the product, often caused by less than ideal design decisions.
70
What are the Scrum pillars?
Transparency, inspection, and adaptation.
71
Define Velocity in Scrum.
An indication of the amount of Product Backlog turned into an Increment during a Sprint.
72
Individuals and interactions over…
Processes and tools
73
Working software over…
Comprehensive documentation
74
Customer collaboration over…
Contract negotiation
75
Responding to change over…
Following a plan