Scrum Events

Question 1

Are the heartbeat of Scrum,

Answer 1

Sprint

Question 2

The Scrum Team turns a selection of the work
into an Increment of value during a…

Answer 2

Sprint

Question 3

Are fixed length events of one month or less
to create consistency

Answer 3

Sprint

Question 4

a container for all other events -
All the work necessary to achieve the Product
Goal, including Sprint Planning, Daily Scrums,
Sprint Review, and Sprint Retrospective,
happen within…

Answer 4

Sprint

Question 5

A new Sprint starts immediately after the
conclusion of the previous Sprint.

Answer 5

Sprint

Question 6

All the work necessary to achieve the Product
Goal, including Sprint Planning, Daily Scrums,
Sprint Review, and Sprint Retrospective,
happen within…

Answer 6

Sprint

Question 7

enable predictability by ensuring
inspection and adaptation of progress toward
a Product Goal at least every calendar month

Answer 7

Sprint

Question 8

Each “…” may be considered a short project

Answer 8

Sprint

Question 9

could be cancelled if the Sprint Goal
becomes obsolete

Answer 9

Sprint

Question 10

Only the Product Owner has the authority to
cancel the…

Answer 10

Sprint

Question 11

Working in “…” at a sustainable pace
improves the Scrum Team’s focus and
consistency

Answer 11

Sprint

Question 12

No changes are made that would endanger
the Sprint Goal

Answer 12

Sprint

Question 13

Quality does not decrease

Answer 13

Sprint

Question 14

Product Backlog is refined as needed

Answer 14

Sprint

Question 15

The Sprint Goal is the single objective for the “…”

Answer 15

Sprint

Question 16

Scope may be clarified and renegotiated with
the Product Owner as more is learned

Answer 16

Sprint

Question 17

As more is learned during the “…”, plans
created initially are updated frequently and at
least once every day

Answer 17

Sprint

Question 18

Multiple Increments may be created within a “…”

Answer 18

Sprint

Question 19

Working in “…” at a sustainable pace
improves the Scrum Team’s focus and
consistency

Answer 19

Sprint

Question 20

is timeboxed to a maximum of eight hours for a one-month Sprint.
For shorter Sprints, the event is usually shorter

Answer 20

sprint planning

Question 21

The Product Owner ensures that attendees are prepared to discuss
the most important Product Backlog items and how they map to the
Product Goal

Answer 21

sprint planning

Question 22

The Scrum Team may also invite other people to attend “…” to provide advice

Answer 22

sprint planning

Question 23

Product Backlog items that can be Done by the Scrum Team within
one Sprint are deemed ready for selection in a “…”

Answer 23

sprint planning

Question 24

Topic One: Why is this Sprint valuable?

Answer 24

1. The Product Owner proposes how the product could increase its
   value and utility in the current Sprint.
2. The whole Scrum Team then collaborates to define a Sprint Goal
   that communicates why the Sprint is valuable to stakeholders.
3. The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog
4. The Sprint Goal must be finalized prior to the end of Sprint Planning.

Question 25

Topic Two: What can be Done this Sprint?

Answer 25

1. Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint 2. The Scrum Team may refine these items during this process, which increases understanding and confidence. 3. The more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts

Question 26

Topic Three: How will the chosen work get done?

Answer 26

1. For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done 2. This is often done by decomposing Product Backlog items into smaller work items of one day or less (common practice is to create various “tasks” for the work involved to turn the PBI to an Increment) 34. How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value

Question 27

The purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work

Answer 27

daily scrum

Question 28

To reduce complexity, it is held at the same time and place every working day of the Sprint.

Answer 28

daily scrum

Question 29

Is a 15-minute event for the Developers

Answer 29

daily scrum

Question 30

If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers

Answer 30

daily scrum

Question 31

The Developers can select whatever structure and techniques they want, as long as this event focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work

Answer 31

daily scrum

Question 32

This event improves communications, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings

Answer 32

daily scrum

Question 33

The Daily Scrum is not the only time Developers are allowed to adjust their (Sprint) plan.

Answer 33

They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s work

Question 34

The Sprint Backlog] should have enough detail that they can inspect their progress in the...

Answer 34

daily scrum

Question 35

Not part of Scrum (as of Nov 2020), but complimentary practice - Developers answer 3 questions with respect to the Sprint Goal

Answer 35

– (a) what did I do yesterday to help the team achieve the Sprint Goal (b) what am I looking to do today to help the team achieve the Sprint Goal (c) what impediments do I have that is slowing me/others in achieving Sprint Goal?

Question 36

purpose of this meeting is to inspect the outcome of the Sprint and determine future adaptations.

Answer 36

sprint review

Question 37

It is the second to last event of the Sprint

Answer 37

sprint review

Question 38

It is timeboxed to a maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter

Answer 38

sprint review

Question 39

the sum of the Increments is presented at the "..." thus supporting empiricism

Answer 39

sprint review

Question 40

The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed

Answer 40

sprint review

Question 41

The Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment

Answer 41

sprint review

Question 42

Based on this information, attendees collaborate on what to do next

Answer 42

sprint review

Question 43

PO’s decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the "...'"

Answer 43

sprint review

Question 44

The Product Backlog may also be adjusted (adapted) to meet new opportunities

Answer 44

sprint review

Question 45

It is a working session and the Scrum Team should avoid limiting it to a presentation

Answer 45

sprint review

Question 46

should never be considered a gate to releasing value.

Answer 46

sprint review

Question 47

If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the "..."

Answer 47

sprint review

Question 48

The purpose is to plan ways to increase quality and effectiveness

Answer 48

sprint retrospective

Question 49

This event concludes the Sprint

Answer 49

sprint retrospective

Question 50

sprint retrospectiveThe Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done

Answer 50

sprint retrospective

Question 51

Inspected elements often also vary with the domain of work

Answer 51

sprint retrospective

Question 52

Also, assumptions that led the Scrum Team astray are identified and their origins explored

Answer 52

sprint retrospective

Question 53

The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved

Answer 53

sprint retrospective

Question 54

The Scrum Team identifies the most helpful changes to improve its effectiveness

Answer 54

sprint retrospective

Question 55

The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint

Answer 55

sprint retrospective