Agile Manifesto & Principles
Roles and Responsibilities
Product & Sprint Backlog
Sprint Ceremonies
User Story and Estimation
100

Individuals and interactions over ____ and ____

Process and Tools

100
__________ facilitates scrum meetings
Scrum Master
100

According to Gretchen,  a product backlog should never have this kind of JIRA case in it. 

Task

100

___________ meeting where everyone is invited to the team’s presentation

Sprint Review

100

This is the list of requirements that a user story must adhere to for the team to call it complete, and is consistent across all user stories.

Definition of Done

200

Customer collaboration over _____ _____

Contract Negotiation

200

__________ defines and prioritizes the product backlog

the Product Owner

200

According to SCRUM, a product is complete when every story on the product backlog is implemented. (true or false)

False. 

In reality, at least 40% of the backlog will never be implemented. This is why we groom only 2-3 sprints worth of stories at a time, maximizing our time panning the highest value for our customer. 

200

In this meeting, the team agrees on what work will be done in the sprint and how the stories will be worked on. 

Sprint Planning

200

_________ identifies the functionality that will deliver business value.

User Story

300

Working software over _____ _____

comprehensive documentation


300

__________ determines “The How” the work will be done

Cross-Functional Team

300

__________ is a collection of high level requirements, represented by User Stories, that will deliver business value

Product Backlog

300

____________ inspects how the last Sprint went with regards to people, relationships, process, and tools

Sprint Retrospective

300

A large user story that awaits decomposition into smaller stories prior to implementation is called______________

an Epic

400

Responding to change over _____ _ _____

following a plan

400
___________ is responsible for removing impediments
Scrum Master
400

_________ is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint

Sprint Backlog

400

____________ meeting is focused on prioritized stories that are targeted for the next 1-2 sprints

Backlog Refinement (Grooming)

400

_________________ are the conditions that a software product must satisfy to be accepted by a user

Acceptance Criteria

500
The best architectures, requirements, and designs emerge from ____________ teams
self-organizing
500

_______ clarifies requirement questions

the Product Owner

500

____________ is negotiated by the team and should be bounded by the team's expected velocity.

The Sprint or the Sprint Backlog

500

The daily standup is the equivalent of a daily status report. True or false.

False. 

The standup is critical for keeping the team in sync and revealing blockers, but should be no longer than 15 minutes in length.

500

Which term below does NOT apply as criteria for a good user story? 

Independent,  Negotiable, Valued, Estimate-able, Small, Testable, Interesting

Interesting

M
e
n
u