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
_________ expressed such that each item has value to the users or customers of the product
Product Backlog
100
___________ meeting where everyone is invited to the team’s presentation
Sprint Review
100
Stories are sized in this format 1,2,3,5,8,13,21 … What is this format called?
Fibonacci sequence
200
Customer collaboration over _____ _____
Contract Negotiation
200

__________ defines and prioritizes the product backlog

Product Owner

200

_________is about planning multiple Sprints, in order to predict when a release(s) might be delivered

Release Planning

200
_______ has two part meeting. Part one defines the "what" and Part two defines the "how".
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

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

Product Owner

500
____________ is negotiated by the team
Sprint Backlog
500
__________ meeting is for the team to sync up with each other regularly in a sprint
Daily Scrum/ Daily Standup
500

I N V E S T stands for ____________________

Independent | Negotiable | Valued | Estimatable | Small | Testable

M
e
n
u