Agile Manifesto & Principles
Individuals and interactions over ____ and ____
Process and Tools
A Product backlog should never have this kind of JIRA case in it.
Task
___________ meeting where everyone is invited to the team’s presentation
Sprint Review
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
Customer collaboration over _____ _____
Contract Negotiation
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.
_______ has two part meeting. Part one defines the "what" and Part two defines the "how".
Sprint Planning
_________ identifies the functionality that will deliver business value.
User Story
Working software over _____ _____
comprehensive documentation
__________ determines “The How” the work will be done
Cross-Functional Team
__________ 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 _____ _ _____
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
____________ meeting is focused on prioritized stories that are targeted for the next 1-2 sprints
Backlog Refinement (Grooming)
_________________ are the conditions that a software product must satisfy to be accepted by a user
Acceptance Criteria
____________ is negotiated by the team
Sprint Backlog
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.
Which term below does NOT apply as criteria for a good user story?
Independent, Negotiable, Valued, Estimate-able, Small, Testable, Interesting
Interesting