Scrum

Question 1

When was SM invented?

Answer 1

Early 90’s

Question 2

When was the SG written?

Answer 2

2010

Question 3

Who created SM?

Answer 3

Jeff Sutherland & Ken Schwaber

Question 4

What is the definition of SM?

Answer 4

Helps people, teams and orgs to generate value through adaptive solutions for complex problems.

Question 5

What is STheory?

Answer 5

1. Empiricism and lean thinking
2. Optimizes predictability and risk control.

Question 6

What are 3 pillars of STheory?

Answer 6

1. Transparency
2. Inspection
3. Adaptation

Question 7

What is transparency?

Answer 7

The process and work must be visible to those performing and receiving the work.

Question 8

What are consequences of low transparency?

Answer 8

Decision that diminish value and increase risk.

Question 9

What does transparency enable?

Answer 9

Inspection. Inspection without transparency is misleading and wasteful.

Question 10

What is a bottleneck to adaption?

Answer 10

Unempowered and non self-managing individuals.

Question 11

What are the 5 SM Values?

Answer 11

1. Focus
2. Openness
3. Respect
4. Commitment
5. Courage

Question 12

Who are the 3 players of SM?

Answer 12

1. Scrum Master
2. Product Owner
3. Developers

Question 13

What does a SM do?

Answer 13

Enforce the SG through removing impediments, coaching and events are kept within the timebox.

Question 14

Who manages stakeholder collaboration?

Answer 14

Scrum Master

Question 15

Who helps ST understand the need for clear and concise PB?

Answer 15

Scrum Master

Question 16

What is the Product Owner responsible for?

Answer 16

Creating Product Backlog items and ensuring it is visible and understood.

Question 17

What are Developers responsible for?

Answer 17

Creating a plan for the Sprint or Sprint Backlog, adhering to the Definition of Done and adapting their plan.

Question 18

How many people should be in a Scrum Team?

Answer 18

10 or fewer.

Question 19

What is a Scrum Event?

Answer 19

Formal opportunity to inspect and adapt artifacts.

Question 20

How long should a Sprint be?

Answer 20

1 month or less.

Question 21

When does a new Sprint start?

Answer 21

Right after the conclusion of a previous one.

Question 22

What happens during a Sprint?

Answer 22

The Product Backlog is refined as needed.

Question 23

What happens when a Sprint is too long?

Answer 23

Could become too complex and risk can arise.

Question 24

When can Sprints be cancelled?

Answer 24

If the Sprint Goal becomes obsolete.

Question 25

Who has the authority to cancel the Sprint?

Answer 25

The Product Owner.

Question 26

What is the purpose of Sprint Planning?

Answer 26

To lay out the work to be performed for the Sprint.

Question 27

Who is the Sprint Planning created by?

Answer 27

Entire Scrum Team.

Question 28

Who can come to the Sprint Planning?

Answer 28

The Scrum team and invited outsiders to provide advice.

Question 29

What questions should be asked during Sprint Planning?

Answer 29

1. Why is this Sprint valuable? 2. What can be done in this Sprint? 3. How will the chosen work get done?

Question 30

What is the timebox of Sprint Planning?

Answer 30

A maximum of 8 hours for a 1 month Sprint.

Question 31

How long should a Daily Scrum be?

Answer 31

15 minutes.

Question 32

When do non-Developers participate as Developers?

Answer 32

If the Product Owner or Scrum Master are actively working on items in the Scrum Backlog.

Question 33

What is the purpose of a Scrum Review?

Answer 33

Inspection of the outcome of the Sprint and determine future adaptions.

Question 34

What is the timebox of a Scrum Review?

Answer 34

Maximum of 4 hours for a 1 month Sprint.

Question 35

What is the purpose of a Sprint Retrospective?

Answer 35

Plan ways to increase quality and effectiveness for the next Sprint by evaluating the previous Sprint.

Question 36

What is a Sprint Artifact?

Answer 36

Represents work or value

Question 37

What is a Product Backlog?

Answer 37

Ordered list of what is needed to improve the product

Question 38

What is a Product Goal?

Answer 38

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

Question 39

What items does a Sprint Backlog consist of?

Answer 39

1. Sprint Goal (Why) 2. Set of Product Backlog Items selected for the Sprint (What) 3. Actionable plan for delivering the Increment (How)

Question 40

How much detail should be in a Sprint Backlog?

Answer 40

Enough for Developers to inspect their progress in the Daily Scrum.

Question 41

What is the Sprint Goal?

Answer 41

Single objective for the Sprint.

Question 42

When is a Sprint Goal created?

Answer 42

During the Sprint Planning.

Question 43

Where can the Sprint Goal be found?

Answer 43

In the Sprint Backlog.

Question 44

What is an Increment?

Answer 44

A stepping stone towards the Product Goal.

Question 45

What is Definition of Done?

Answer 45

State of the increment when it meets quality measures required for the product.

Question 46

When does a Product Backlog become an Increment?

Answer 46

When a Product Backlog meets the Definition of Done it becomes an Increment.

Question 47

What happens if a Product Backlog does not meet the Definition of Done?

Answer 47

It is not presented in the Scrum Review and returns to the Product Backlog for future consideration.