Scrum Fundamentals

Events

100

This time-boxed event happens daily for Scrum teams to synchronize activities.

1. (What is the Daily Scrum?)

200

This is a fixed-length iteration in Scrum, typically lasting 1-4 weeks.

1. (What is a Sprint?)
2. 
   

300

This event marks the official start of the Sprint, where planning takes place.

1. (What is the Sprint Planning Meeting?)
2. 
   

400

This Scrum event is for teams to inspect and adapt their process after each Sprint.

1. (What is the Sprint Retrospective?)
2. 
   

500

This event allows stakeholders to see what was completed during the Sprint.

1. (What is the Sprint Review?)
2. 
   

Stuff

100

This Scrum role is responsible for maximizing the product's value.

1. (Who is the Product Owner?)
2. 
   

200

This Scrum role facilitates the process and helps remove impediments.

1. (Who is the Scrum Master?)
2. 
   

300

This role collectively is responsible for delivering the Sprint increment.

1. (Who are the Developers or the Development Team?)
2. 
   

400

This artifact provides visibility into the current state of Sprint work.

1. (What is the Sprint Backlog?)
2. 
   

500

Scrum is based on these three pillars: transparency, inspection, and this.

1. (What is adaptation?)
2. 
   

Even More Stuff

100

This document lists all desired features, changes, and fixes for the product.

1. (What is the Product Backlog?)
2. 
   

200

This artifact shows what will be worked on during the Sprint.

1. (What is the Sprint Backlog?)
2. 
   

300

The Product Owner manages this collection of prioritized work items.

1. (What is the Product Backlog?)
2. 
   

400

This process helps Product Owners prioritize work for maximum value.

1. (What is Backlog Refinement or Grooming?)
2. 
   

500

This is the official name of the Scrum guide released by the framework’s creators.

1. (What is the Scrum Guide?)
2. 
   

Terms and Such

100

This term refers to a potentially shippable product increment created at the end of each Sprint.

1. (What is the Increment?)
2. 
   

200

This describes the criteria that must be met for a Product Backlog item to be considered ‘done’.

1. (What is the Definition of Done?)
2. 
   

300

The Scrum Master is not a manager, but serves the team in this capacity.

1. (What is a servant leader?)
2. 
   

400

Scrum teams commit to this number of Product Owners per team.

1. (What is one?)
2. 
   

500

This popular agile framework was co-created by Ken Schwaber and Jeff Sutherland in the 1990s.

1. (What is Scrum?)

Guess What? More Scrum

100

This principle limits the time allocated to meetings and events in Scrum.

1. (What is Timeboxing?)
2. 
   

200

This is what happens if work is not completed by the end of the Sprint.

1. (What is moved back to the Product Backlog? Or Next Sprint? )
2. 
   

300

This event can help teams identify ways to improve for the next Sprint.

1. (What is the Sprint Retrospective?)
2. 
   

400

In Scrum, this meeting is short, focused, and answers three questions: What did you do yesterday? What will you do today? Are there any blockers?

1. (What is the Daily Scrum?)
2. 
   

500

Scrum advocates for teams of this size range.

1. (What is 3 to 9 members?)
2. I will also accept 4-6
3. I will also except "less than ten"