Scrum Theory
Values
Team
Events
Artifacts
100

What values are the Scrum methodology Founded on? 

 

A: empiricism and lean thinking

100

 Name one of the five Scrum values. 

What is Commitment, Focus, Openness, Respect, or Courage? 

100

This role helps the team work better, fixes problems that slow them down, and teaches everyone how to use Scrum correctly.

What is the Product Owner?

100

This event starts the Sprint and sets the plan for what the team will deliver.


What is Sprint Planning?

100

What are the three core artifacts defined by Scrum?

  • (A) Product Backlog, Sprint Backlog, Increment
  • (B) Product Roadmap, Sprint Plan, Release Schedule
  • (C) User Stories, Tasks, Bugs
  • (D) Product Goal, Sprint Goal, Definition of Done.  

A — Product Backlog, Sprint Backlog, Increment

200

 What type of approach does the Scrum take when faced with a problem/task 

    

    A: an iterative, incremental approach

200

Which value encourages team members to speak honestly about progress and problems they may have? 

What is Openness?   

200

This accountability coaches the team, removes impediments, and ensures Scrum is understood.

Who is the Scrum Master?

200

This event happens every day and helps the Developers inspect progress toward the Sprint Goal.


What is the Daily Scrum?

200
  • Which Scrum artifact represents everything known that needs to be done to build or improve the product?
  • (A) Sprint Backlog
  • (B) Product Backlog
  • (C) Increment
  • (D) Definition of Done  

B — Product Backlog

300

What happens if a task is not completed by the end of a sprint? 

   

 A: Reflection is done, and the task is placed back into the product backlog for a future sprints

300

This value helps team members take on difficult challenges with no fear. 

What is Courage? 

300

These team members turn Product Backlog Items into a usable “Done” Increment each Sprint.

Who are the Developers?

300

This event is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog.


What is the Sprint Review?

300
  • What two things together define the content of the Sprint Backlog?
  • (A) List of Product Backlog items selected for the Sprint, and a plan for delivering them
  • (B) List of all features planned for the product, and the product roadmap
  • (C) Completed items, and quality checklist
  • (D) Team roles, and Sprint Goal

A — Selected Product Backlog items + a plan for delivering them

400

How long is a sprint allowed to last? 

  

A: 4 weeks max, 1 week min

400

This value makes it clear that everyone on the team needs to be kind and treat each other with politeness.  

 What Is Respect?    

400

This group (all three accountabilities together) is responsible for delivering a valuable, usable Increment every Sprint.

What is the Scrum Team?

400

This event is a team-focused reflection where the Scrum Team discusses how to improve for the next Sprint.



What is the Sprint Retrospective?

400

What does the “Increment” artifact represent at the end of a Sprint?

  • (A) The prioritized list of what to build next
  • (B) The set of tasks for the next Sprint
  • (C) The sum of all Product Backlog items completed in this Sprint (plus all previous Sprints), meeting the agreed “Definition of Done”
  • (D) The team’s velocity and capacity forecast  

C — The sum of all completed Product Backlog items (this Sprint + previous), meeting the Definition of Done

500

500: What is the end goal of a scrum team? 

   

  A: Creating a team of developers that can think critically as individuals

500

This Scrum value supports delivering the highest quality work while minimizing distractions. 

What is Focus?  

500

True or False: The Product Owner and Scrum Master may also serve as Developers as long as they still fulfill their primary accountability.

True.

500

This event contains all other Scrum events and lasts a fixed timebox of one month or less.


What is the Sprint?

500
  • Why are Scrum artifacts designed to include a “commitment” (like Product Goal, Sprint Goal, Definition of Done)?
  • (A) To make sure team members are punished for failing
  • (B) To provide transparency and a shared basis for inspection and adaptation
  • (C) To create a fixed, unchangeable plan for the project
  • (D) To avoid meetings and documentation. 

B — To provide transparency and a shared basis for inspection and adaptation

M
e
n
u