Individuals and interactions over ____ and Tools
Process
__________ facilitates scrum meetings
Scrum Master
_________ expressed such that each item has value to the users or customers of the product
Product Backlog
___________ meeting where everyone is invited to the team’s presentation
Sprint Review
Stories are sized in this format 1,2,3,5,8,13,21 … What is this format called?
Fibonacci sequence
Customer collaboration over _____ and Negotiation
Contract
_________is about planning multiple Sprints, in order to predict when a release(s) might be delivered
Release Planning
_______ has two part meeting. Part one defines the "what" and Part two defines the "how".
Sprint Planning
_________ sizes User Stories
The Team
Working software over comprehensive _____
documentation
__________ is a collection of high level requirements, represented by User Stories, that will deliver business value
Product Backlog
____________ inspects how the last Sprint went with regards to people, relationships, process, and tools
Sprint Retrospective
A large user story that awaits decomposition into smaller stories prior to implementation is called______________
an Epic
Responding to change over _____ a _____
following a plan
_________ is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint
Sprint Backlog
_________________ are the conditions that a software product must satisfy to be accepted by a user
Acceptance Criteria
The best architectures, requirements, and designs emerge from ____________ teams
self-organizing
____________ is the set of Product Backlog items selected for the Sprint
What is the Sprint Backlog
I N V E S T stands for ____________________
Independent | Negotiable | Valued | Estimatable | Small | Testable