Daily Scrum
Sprint Planning
Sprint Review
Retrospective
The Sprint
100
Three questions that are no longer an official part of the Daily Scrum as of November 2020
What are:
"What did we get done yesterday"
"What did we do today"
"What impediments are in our way"
100
For what reason do the Developers work as a group to discuss tests and tasks prior to the work being assigned?
What is: the ability for all team members to swarm to support the completion of the valuable increment
100
This group of individuals should be invited to the Sprint Review
Who is all stakeholders
100
It is a meeting held at the end of a sprint where teams reflect on what went well, what didn’t, and how to improve their processes for future sprints. This practice is essential for continuous improvement in Agile methodologies.
What is a sprint retro
100
This chart is used by teams to assess progress towards the goal on a daily basis
What is the Burndown chart
200
The timebox for the Daily Scrum
What is 15 minutes
200
What are the three main aspects of a Sprint Planning meeting?
What is The Why, The What and The How.
200
This is inspected for improvement in a Sprint Review
What is the Product
200
This is inspected for improvement in the Sprint Retrospective
What is the process
200
This is the recommended timebox for a Sprint
What is anywhere between 1 and 4 weeks
300
Daily Double
This space craft is known as a?
300
Who owns the Sprint Backlog?
Who are: The Developers
300
This only type of work that can be demonstrated in a Sprint Review
What is completed work.
300
A Retro method that repeats the same question several times to get to a root cause
The Five Whys
300
This standard could include criteria such as "tested and defect free" or "Acceptance criteria met"
What is Definition of Done
400
This is inspected and adapted in the Daily Scrum
What is the work necessary to meet the goal
400
This Sprint Planning preparation event is not an official event in the Scrum Guide
What is Refinement
400
A fact-based, experience-based, and evidence-based concept key to the Sprint Review
What is empiricism
400
What Retrospective timebox should not be exceeded for a two-week Sprint Cycle
What is 1.5 hours
400
Daily Double
What does TIE stand for?
500
Which law helps explain the value of the timebox for the Daily Scrum (and all events, really)
What is Parkinson's Law
500
This standard guides teams to know when a story is ready for the Sprint Planning
What is Definition of Ready
500
Rather than a presentation, the Sprint Review is considered a way to gather what
What is feedback
500
In this nautically-themed retro technique, anchors are used as a metaphor for the bottlenecks your team has encountered
What is Sailboat
500
This source states that a Sprint can be considered a small project
What is the Scrum Guide