Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Scrum > Scrum Events > Flashcards

Scrum Events Flashcards

1
Q

Are the heartbeat of Scrum,

A

Sprint

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

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

A

Sprint

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

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

A

Sprint

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

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…

A

Sprint

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

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

A

Sprint

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

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

A

Sprint

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

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

A

Sprint

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

Each “…” may be considered a short project

A

Sprint

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

could be cancelled if the Sprint Goal
becomes obsolete

A

Sprint

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

Only the Product Owner has the authority to
cancel the…

A

Sprint

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

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

A

Sprint

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

No changes are made that would endanger
the Sprint Goal

A

Sprint

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

Quality does not decrease

A

Sprint

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

Product Backlog is refined as needed

A

Sprint

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

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

A

Sprint

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

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

A

Sprint

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

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

A

Sprint

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

Multiple Increments may be created within a “…”

A

Sprint

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

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

A

Sprint

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

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

A

sprint planning

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

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

A

sprint planning

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

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

A

sprint planning

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

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

A

sprint planning

24
Q

Topic One: Why is this Sprint valuable?

A
  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.
25
Q

Topic Two: What can be Done this Sprint?

A
  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
26
Q

Topic Three: How will the chosen work get done?

A
  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)
  3. 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
27
Q

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

A

daily scrum

28
Q

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

A

daily scrum

29
Q

Is a 15-minute event for the
Developers

A

daily scrum

30
Q

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

A

daily scrum

31
Q

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

A

daily scrum

32
Q

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

A

daily scrum

33
Q

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

A

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

34
Q

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

A

daily scrum

35
Q

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

A

– (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?

36
Q

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

A

sprint review

37
Q

It is the second to last event of the
Sprint

A

sprint review

38
Q

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

A

sprint review

39
Q

the sum of the Increments is
presented at the “…” thus
supporting empiricism

A

sprint review

40
Q

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

A

sprint review

41
Q

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

A

sprint review

42
Q

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

A

sprint review

43
Q

PO’s decisions are visible in the
content and ordering of the Product
Backlog, and through the inspectable
Increment at the “…’”

A

sprint review

44
Q

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

A

sprint review

45
Q

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

A

sprint review

46
Q

should never be considered a gate to releasing value.

A

sprint review

47
Q

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

A

sprint review

48
Q

The purpose is to plan ways
to increase quality and
effectiveness

A

sprint retrospective

49
Q

This event concludes the
Sprint

A

sprint retrospective

50
Q

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

A

sprint retrospective

51
Q

Inspected elements often also
vary with the domain of work

A

sprint retrospective

52
Q

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

A

sprint retrospective

53
Q

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

A

sprint retrospective

54
Q

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

A

sprint retrospective

55
Q

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

A

sprint retrospective

Scrum (3 decks)

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