Scrum Events Flashcards

1
Q

g

What are the four Scrum Events?

A
  • Daily Standup
  • Sprint Planning
  • Sprint Review
  • Sprint Retrospective
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the key elements of Sprint Planning

A
  • Process of selecting PBIs for next sprint.
  • Transform the Product Backlog into an actionable plan for a product increment.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the Sprint Planning Meeting Inputs

A
  • Ordered product backlog
  • Record of completed BPIs from previous product increments
  • Knowledge of past performance of team
  • Dev team capacity
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the Sprint Planning Meeting Outputs?

A
  • Sprint Backlog
  • Sprint Goal
  • Sprint Plan
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is Backlog Refinement?

A

Goal is to ensure BPIs are well-defined, prioritized & ready for inclusion in upcoming Sprints.

  • Can happen anytime
  • Improvements and adjustments to BPI’s based upon on new or changed information.
  • Progressive elaboration
  • Team collaboration
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the Daily Scrum and what are the organizational rules?

A
  • Max 15 minutes a day.
  • Every day - same time and (if on-site) location.
  • Scrum alliance says entire team attends
  • Only Devs speak
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is the result of the Sprint Review? Select one answer.

a) A list of improvements that the Scrum Team will implement in the next Sprint
b) A revised Product Backlog that defines the probable Product Backlog items for the next Sprint
c) Common understanding of what can be delivered in the Increment and how will the work needed to deliver the Increment be achieved
d) Common understanding of progress toward the Sprint Goal and how progress is trending toward completing the work in the Sprint Backlog

A

b

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

What is the time-box for the Sprint Review? The sprint is assumed to be 4 weeks long.

a) 3 hours
b) 4 hours
c) It depends on how much work was done in the previous sprint
d) 2 hours

A

4 hours

b

4 hours

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

Product Backlog Refinement practice focuses on items for upcoming Sprints, not the current Sprint.

True
False

A

False

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

During the Sprint, the Sprint Goal can be changed?
True
False

A

False

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

During the Sprint, if new work is required, the Developers can add it to the current Sprint Backlog.
True
False

A

True

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

Who must ensure the new increment meets the Definition of Done?
1. Scrum Master
2. Product Owner
3. Developers
4. Scrum Team
5. QA Specialists

A

3

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

How much of the Sprint Backlog must be defined during the sprint Planning meeting?
1. Just enough to understand design & architectural implications
2. Entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning meeting
3. Enough so the Developers can create their best forecast of work they can complete, and to start the first several days of the Sprint
4. Just enough tasks for the Scrum Master to be confident in the Developer’s understanding of the Sprint

A

3

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

A Sprint could be cancelled if the Sprint Goal becomes obsolete.
True
False

A

True

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

Multiple Scrum Teams working on the same project must have the same Sprint start date
True
False

A

False

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

Who is allowed to change the Sprint Backlog during the Sprint?
1. Developers
2. Devs & PO
3. Scrum Team
4. PO
5. Scrum Master

A

1

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

What topics should be discussed at the Sprint Review?
1. Coding & engineering practices
2. Sprint results
3. The Scrum process and how it was used during the Sprint
4. All of the above

A

2

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

When does the Sprint end?
1. Immediatelly after the Sprint Review
2. When the time-box expires
3. When there is no work remaining in the Sprint Backlog
4. It depends upon the Product Owner

A

2

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

What are the properties of the Daily Scrum? (2 answers)
1. Scrum Master asking team members the 3 questions
2. Facilitated by the Team Lead
3. 15 minutes in duration
4. Location & time should remain constant
5. Held first thing in the morning
6. It is free-form & designed to promote conversation

A

3 & 4

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

Multiple Sprint Teams working on the same must have the same Sprint start date.
True
False

A

False

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

What is the outcome of the Sprint Review?
1. A new increment ready to be released.
2. A revised Sprint Goal
3. A revised Product Backlog
4. A revised Definition of Done
5. A revised Sprint Backlog

A

3

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

Which of the following statements are true? Select all that apply
1. After the Sprint Planning, a Sprint cannot proceed without a Sprint Goal.
2. After the Sprint Planning, a Sprint cannot proceed without a complete requirements specification
3. After the Sprint Planning, a Sprint cannot proceed without a complete Sprint Backlog
4. After the Sprint Planning, a Sprint cannot proceed without a complete architecture

A

1 & 3

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

When does a Sprint end?
1. Immediately after the conclusion of the Sprint Review
2. When the time-box expires
3. It depends on the PO.
4. When there is no work remaining in the Sprint Backlog

A

2

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

An increment can only be delivered to stakeholders at the Sprint Review.
* True
* False

A

False

An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable.

Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.

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

What is the maximum amount of time that the team should spend in the Daily Scrum?
1. As long as it takes
2. 1 hour
3. 45 minutes
4. 15 minutes
5. 15 minutes, proportionally less for shorter Sprints

A

4

26
Q

Which of the following activities do not occur at the end of the Sprint? (Choose two)
1. Software development
2. Release deployment
3. Sprint review meeting
4. Quality assurance testing

A

1,4

27
Q

The Sprint planning meeting is comprised of how many sections?
1. 4
2. 3
3. 2
4. 1

A

3

Part 1: Scope and Objective (What) - what items will be worked on in the upcoming sprint?
Part 2: Scope and Objective (How) - how will the items in the sprint be completed?

28
Q

What is the maximum duration of each Sprint planning meeting section
1. 1 hour
2. 30 minutes
3. 4 hours
4. 2 hours
5. 15 minutes

A

3

29
Q

Which event is the latest step in the Scrum framework sequence?
1. Daily Scrum
2. Sprint Retro
3. Sprint Review
4. Sprint Planning

A

2

30
Q

What is the primary objective of the Daily Scrum?
1. To share with the team what each member has completed in the Sprint, what they will work on next and to report any progress roadblocks
2. To give a status report to the PO on what each member has completed in the Sprint, what they will work on next and to report any progress roadblocks
3. To discuss work details with the team since every team member must attend the meeting
4. To give a status report to the Scrum Master on what each member has completed in the Sprint, what they will work on next and to report any progress roadblocks

A

1

31
Q

Which statement best describes what it means for an activity to be time-boxed?
1. The activity must take place on a particular date
2. The activity must start at a particular time
3. There is a maximum time limit for the activity
4. There is a recommended amount of time for the activity

A

3

32
Q

Which statement best describes the primary objective of the Sprint Review?
1. to demo the Sprint work for Senior Management.
2. to demo the Sprint work and receive feedback from the PO on the work completed in the Sprint.
3. to demo the work and to receive feedback from the Scrum Master on the work completed in the Sprint.
4. To demo the Sprint work and to recommend ways to work better in the Sprint.

A

2

33
Q

Which of the following is not a Scrum cycle activity?
1. Sprint Retro
2. Daily Scrum
3. Weekly Inspection
4. Sprint Planning

A

3

34
Q

Which statement below best describes the primary objective of the Sprint Retro?
1. to identify what went wrong or hindered the Sprint.
2. to provide feedback to the PO.
3. to recommend ways to work better in the Sprint
4. to review the work completed by the team during the Sprint

A

3

35
Q

Which of the following is NOT part of the Sprint?
1. The product released to customers after each Sprint
2. The principal goal of a Sprint is to produce release-quality increments in functionality
3. Releases usually incorporate the result of multiple Sprints
4. Occur at times dictated by the customer and business needs

A

1

36
Q

What happens when all committed items (requirements) are not completed at the end of the Sprint?
1. The Sprint duration is extended.
2. The tasks are determined to be unncessary.
3. The items are returned to the Product Backlog.
4. None of the above

A

3

37
Q

The recommended time of day to hold the daily Scrum meeting is:
1. The beginning of the day
2. Right after lunch
3. 4:30 PM
4. 7:00 PM

A

1

38
Q

What happens when the Sprint is cancelled?
1. The Scrum Team disbands
2. The complete Sprint backlog is put back into the Product Backlog
3. The completed Sprint items are evaluated for a release and incomplete items are ignored.
4. The completed Sprint items are evaluated for a release and incomplete items are put back into the Product Backlog.

A

4

39
Q

When should the Product Owner ship or implement a Sprint Increment?
1. At the end of every Sprint.
2. When the Team feels it is done with each Sprint.
3. Whenever the increment is free of defects.
4. When it makes sense.

A

4

40
Q

Who attends the Daily Scrum?
1. The Dev Team
2. The Product Owner
3. The Scrum Master
4. All of the above

A

4

41
Q

What is the primary purpose of the Sprint Retro?
1. To reflect on the positives and negatives of the previous Sprint.
2. To look at improvemetns that can be made to the development process.
3. A chance for team members to journal their thoughts.
4. To give everyone an opportunity to discuss what they think about the product so far.

A

2

42
Q

What is the time-box for planning a two-week Sprint?
1. 4 hours
2. 6 hours
3. 8 hours
4. 10 hours

A

1

43
Q

What is the max length of a Sprint?
1. Up to 2 weeks
2. Up to 3 weeks
3. Up to 4 weeks
4. As long as the Scrum team sets

A

3

44
Q

What is the time-box for a Sprint Retro after a 1 month Sprint?
1. 2 hours
2. 3 hours
3. 4 hours
4. 5 hours

A

2

45
Q

What is the Purpose of the Sprint Review?
1. To review the Product Increments.
2. To adjust the Product Backlog.
3. For Stakeholders to review the products created.
4. All of the choices are correct.

A

4

46
Q

What is the time-box of a Daily Scrum?
1. 5 minutes
2. 10 minutes
3. 15 minutes
4. 20 minutes

A

3

47
Q

Who attends the Sprint Review?
1. The Dev Team
2. The Scrum Master
3. Product Stakeholders
4. All of the above.

A

4

48
Q

When does a Sprint start?
1. The Monday after the previous Sprint ends.
2. The first working day of the month.
3. As soon as the previous Sprint ends.
4. The day after the previous Sprint ends.

A

3

49
Q

A Sprint Retrospective can last up to 8 hours in a month-long Sprint.
True
False

A

False. No longer than 3 hours for a 1 month Sprint.

50
Q

What pre-conditions must be fulfilled in order to allow Sprint Planning to begin?
1. A fully refined Product Backlog
2. A clear and non-negotiable Sprint Goal
3. Enough “Ready Product Backlog Items to fill the Sprint
4. Formal budget approval to conduct another Sprint.
5. There are no such pre-conditions.

A

5

Sprint Planning serves to plan the work to be performed in the Sprint. T

51
Q

There can be a maximum of one release per Sprint
True
False

A

False

You can have more than one release per Sprint, if needed.

When you use continuous integration and have a Definition of Done that covers everything, you can practically release the product at any time you want (think of it as a typical DevOps environment). The Increments that are created at the end of the Sprint are NOT the only potentially releasable products; they are just packaged and named like this, to be used for receiving feedback at certain intervals.

52
Q

Select all that apply. For a Scrum Team, the Sprint Planning meetings are always going beyond the time-box. What could the likely causes be?
1. The Scrum Master does not moderate & control the participants.
2. The team did not invest enough time and effort in Product Backlog refinement.
3. The Product Backlog size is huge
4. The Developers are trying to get a perfect and detailed Sprint Plan.

A

1 & 4

If the team doesn’t invest enough in Product Backlog refinement the Sprint Planning can take longer as the Product Backlog Items lack information such as description and estimation. The Scrum Team is therefore less likely to forecast the necessary work to deliver a valuable and usable increment that meets the Definition of Done.

53
Q

The three questions must always be answered during the Daily Scrum.
True
False

A

False

It’s best practice, but NOT mandatory.

54
Q

The structure of the Daily Scrum is well-defined and constant. Every Developer should answer the three main questions:

What did I do yesterday?
What will I do today?
Do I see any impediment?

True
False

A

False

There is not any prescribed structure. The structure of the Daily Scrum is set by the Developers and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Developers will use questions, some will be more discussion based. It is still perfectly fine to use the questions, but other ways of conducting the meeting are also possible.

55
Q

What is the maximum length of the Sprint Planning in a project with three-week Sprints?
1. 6 hours
2. 3 hours
3. 4 hours
4. 8 hours

A

1

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

Important note :

Be careful, the concept of proportionality was effective in the 2013 version of the Scrum Guide but it’s been abandoned since the 2017 version of the Scrum Guide. So since 2017, the MAXIMUM length of the Scrum Events are 15 mins for the Daily Scrum, 8 hours for the Sprint Planning, 4 hours for the Sprint Review and 3 hours for the Sprint Retrospective no matter the length of the Sprint.

56
Q

Who participate in the Sprint Review? Select all applicable variants.
1. Product Owner
2. Devs
3. Organization CEO
4. Key Stakeholders
5. Scrum Master

A

1,2,4 & 5

During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.

57
Q

When does inspection occur?
1. At the Sprint Review
2. All the time
3. When the PO feels it is necessary
4. Frequently, but no so often as to get in the way of work.

A

4

All Scrum events are opportunities for inspection and adaptation. Inspection makes adaptation possible and that’s why it’s important. However, like anything else in Agile, we just like to have “enough” of it.

58
Q

What are the prerequisites for starting a Sprint Planning (choose the best answer)
1. User Stories that conform with the Definition of Ready.
2. A fully refined Product Backlog
3. Approval from the Steering Committee
4. There are no such prerequisites
5. The preparedness of the PO.
6. Availability of key Scrum Team members.

A

4

Explanation
“A new Sprint starts immediately after the conclusion of the previous Sprint.”
- The Scrum Guide (TM) of 2020.

Scrum events should be held at the same time each Sprint. This helps with consistency, making improvements to the process, and reducing waste. In an event that a Scrum event cannot begin at the Scrum Team’s designated time, they will need to inspect and adapt the event itself in order to maximize the effectiveness of the event. Delaying events is a short-term solution and results in reducing the team’s opportunities to improve.

59
Q

It is a good practice to have from time to time a special technical Sprint that consists only of tasks removing the technical debt without implementing any new functionality.
True
False

A

False

It is prohibited. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done.”

60
Q

What should happen to the “Done” Product Backlog items when the Sprint is cancelled?
1. They should be moved to the next Sprint Backlog.
2. They will be reviewed, and if they are potentially releasable, the Product Owner typically accepts them.
3. They should be moved to the Product Backlog, and would be taken care of in the future Sprints.

A

2