Untitled Deck

Question 1

What is Scrum?

Answer 1

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

Question 2

Scrum originators

Answer 2

Ken Schwaber and Jeff Sutherland; first co-presented Scrum publicly at OOPSLA 1995.

Question 3

Scrum Guide licensing

Answer 3

Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0).

Question 4

Core theory

Answer 4

Empiricism (knowledge from experience) and Lean thinking (reduce waste, focus on essentials).

Question 5

Empirical pillars

Answer 5

Transparency, Inspection, Adaptation.

Question 6

Scrum values

Answer 6

Commitment, Focus, Openness, Respect, Courage.

Question 7

Fundamental unit

Answer 7

Scrum Team (one Product Owner, one Scrum Master, and Developers).

Question 8

Team traits

Answer 8

Cross-functional and self-managing; no sub-teams or hierarchies.

Question 9

Typical team size

Answer 9

10 or fewer people; reorganize into multiple teams if too large.

Question 10

Whole-team accountability

Answer 10

Entire Scrum Team is accountable for creating a valuable, useful Product Increment each Sprint.

Question 11

Developers - key accountabilities

Answer 11

Create the Sprint Backlog plan, ensure quality via Definition of Done, adapt plan daily toward Sprint Goal, and hold each other accountable.

Question 12

Product Owner -core accountability

Answer 12

Maximize product value resulting from the Scrum Team’s work.

Question 13

PO - backlog management

Answer 13

Develop and communicate the Product Goal; create, communicate, and order Product Backlog items; ensure backlog transparency.

Question 14

Product Owner is

Answer 14

One person (not a committee); may delegate work but remains accountable.

Question 15

Scrum Master - core accountability

Answer 15

Establish Scrum and improve team effectiveness; ensure Scrum events occur, coach, remove impediments.

Question 16

Scrum events

Answer 16

Sprint (container), Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.

Question 17

Sprint length

Answer 17

Fixed length of one month or less; a new Sprint starts immediately after the previous ends.

Question 18

During the Sprint (rules)

Answer 18

No changes that endanger the Sprint Goal; quality does not decrease; backlog refined as needed; scope may be clarified/renegotiated with PO.

Question 19

Who can cancel a Sprint?

Answer 19

Only the Product Owner, if the Sprint Goal becomes obsolete.

Question 20

Sprint Planning purpose

Answer 20

Initiates the Sprint and lays out work for the Sprint through collaboration of the full Scrum Team.

Question 21

Sprint Planning topics

Answer 21

1) Why valuable? (define Sprint Goal) 2) What can be done? 3) How will chosen work get done?

Question 22

Sprint Planning output

Answer 22

Sprint Backlog = Sprint Goal + selected backlog items + plan for delivering them.

Question 23

Sprint Planning timebox

Answer 23

Up to 8 hours for a one‑month Sprint (shorter for shorter Sprints).

Question 24

Daily Scrum purpose

Answer 24

Inspect progress toward the Sprint Goal and adapt the plan for the next day’s work.

Question 25

Daily Scrum participants

Answer 25

Developers (PO/SM participate if they are doing Sprint Backlog work).

Question 26

Daily Scrum timebox

Answer 26

15 minutes; same time and place each working day.

Question 27

Sprint Review purpose

Answer 27

Inspect the outcome of the Sprint, discuss progress toward the Product Goal, and collaborate on next steps.

Question 28

Sprint Review timebox

Answer 28

Up to 4 hours for a one‑month Sprint (shorter for shorter Sprints).

Question 29

Sprint Retrospective purpose

Answer 29

Plan ways to increase quality and effectiveness; identify improvements.

Question 30

Sprint Retrospective timebox

Answer 30

Up to 3 hours for a one‑month Sprint (shorter for shorter Sprints).

Question 31

Artifacts

Answer 31

Product Backlog, Sprint Backlog, Product Increment.

Question 32

Artifact commitments

Answer 32

Product Backlog → Product Goal; Sprint Backlog → Sprint Goal; Product Increment → Definition of Done.

Question 33

Product Backlog

Answer 33

Emergent, ordered list and the single source of work for the Scrum Team; refined continuously.

Question 34

Product Goal

Answer 34

Long‑term objective that guides planning; fulfill or abandon before taking on the next.

Question 35

Sprint Backlog

Answer 35

Developers’ plan (why/what/how) updated throughout the Sprint; visible, real‑time picture of work for achieving the Sprint Goal.

Question 36

Sprint Goal

Answer 36

Single objective for the Sprint; provides focus and flexibility on the exact work to achieve it.

Question 37

Product Increment

Answer 37

Usable, additive to prior increments, thoroughly verified; multiple increments may be created in a Sprint; may be released before Sprint end.

Question 38

Definition of Done (DoD)

Answer 38

Formal description of the quality state required; work not meeting DoD cannot be released or even presented; Developers must conform.

Question 39

Organization-wide DoD

Answer 39

If an organizational standard exists, all Scrum Teams must at least meet it; multiple teams working on a product must share the same DoD.

Question 40

Forecasting tools

Answer 40

Burn-downs, burn-ups, cumulative flow—useful but do not replace empiricism.

Question 41

Scrum immutability

Answer 41

Scrum exists only in its entirety; implementing only parts means it is not Scrum.

Question 42

Diagram (p. 43)

Answer 42

Architecture: Empiricism built on Lean Thinking; pillars (Transparency, Inspection, Adaptation) uphold Scrum.