Agile and Scrum Ceremonies Flashcards
7 cards from real Project Management practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Agile and Scrum Ceremonies flashcards as text
What distinguishes a Sprint Retrospective from a Sprint Review in terms of audience?
Answer: The Review includes stakeholders; the Retrospective is for the Scrum Team only
The Sprint Review is an open inspection where stakeholders are invited, while the Sprint Retrospective is an internal Scrum Team ceremony focused on continuous improvement.
Which statement best describes the relationship between the Sprint Goal and Sprint Planning?
Answer: The Sprint Goal is brought by the Product Owner and refined during Sprint Planning
The Product Owner proposes a Sprint Goal before planning, and the Scrum Team crafts the final Sprint Goal collaboratively during Sprint Planning.
A Scrum Team completes its Increment but realizes the Sprint Goal was not fully met. What should happen at the Sprint Review?
Answer: Present what was done, discuss the gap, and adapt the Product Backlog accordingly
The Sprint Review is an inspect-and-adapt event where the team presents the Increment, discusses what happened, and updates the Product Backlog based on new understanding.
What is the maximum timebox for a Daily Scrum?
Answer: 15 minutes
The Daily Scrum is timeboxed to 15 minutes regardless of team size, promoting discipline and efficiency in daily synchronization.
During Backlog Refinement, who is responsible for clarifying the details of Product Backlog items?
Answer: The Product Owner and Developers collaboratively
Backlog Refinement is a collaborative activity where the Product Owner and Developers add detail, estimates, and order to Product Backlog items.
Which Agile principle directly supports the purpose of holding frequent Sprint Reviews?
Answer: Working software is the primary measure of progress
The Agile principle that working software is the primary measure of progress directly supports Sprint Reviews, where teams demonstrate a potentially shippable Increment.
A newly formed Scrum Team asks how long each Sprint should be. What guidance does the Scrum Guide provide?
Answer: Between 1 and 4 weeks, chosen by the team
The Scrum Guide recommends Sprints be one month or less, with the team choosing the specific length to maintain a consistent cadence.