🔄 Scrum Ceremonies Vocabulary
Master the language of daily standups, sprint planning, sprint review, and retrospectives. Intermediate
0 / 25 completed
1 / 25
Your new colleague joins the team standup and asks: "What exactly are we supposed to say during the daily standup?" The Scrum Master replies: "We use the classic three-question format."
Which set of questions correctly describes the standard daily standup three questions?
The three standup questions focus on yesterday, today, and impediments — keeping the team aligned on progress toward the sprint goal:
| Question | Purpose |
|---|---|
| What did I complete yesterday? | Synchronise on progress toward the sprint goal |
| What will I work on today? | Signal intent; surface potential overlaps and conflicts |
| Is anything blocking my progress? | Surface impediments so the team can act quickly |
Option A uses "last week / this week" — that is a weekly status format, not a daily standup. Options C and D describe team-level metrics discussions that belong in sprint planning or retrospectives, not the 15-minute daily standup.
2 / 25
During sprint planning, the Scrum Master says:
"Before we pull stories from the backlog, let's check our capacity for this sprint. Priya is on holiday for 3 days, and we have the company all-hands on Friday afternoon."
In this sprint planning context, what does "capacity" most precisely mean?
Capacity in sprint planning refers to how much work the team can realistically take on — calculated from available person-days minus any absences, company events, and non-development time:
| Term | Definition |
|---|---|
| Capacity | Available focused hours/days this sprint (holidays, all-hands, and sick days deducted) |
| Velocity | Story points completed per sprint (historical average, used alongside capacity for forecasting) |
| Forecast / Commitment | Story points the team plans to deliver, informed by both capacity and velocity |
Teams often express reduced capacity as a percentage: "We are at 80% capacity this sprint." This directly influences how many story points to pull from the backlog during sprint planning.
3 / 25
At the end of Sprint 12, a colleague sends a calendar invite titled "Retrospective" with this description:
"All stakeholders and the product team are welcome. We will be demonstrating the new checkout flow and gathering feedback on the features completed this sprint."
Which Scrum event is actually being described, regardless of the label on the invite?
The Sprint Review and Sprint Retrospective are the two end-of-sprint events and are frequently confused by teams:
| Event | Attendees | Focus |
|---|---|---|
| Sprint Review | Scrum Team + stakeholders | Inspect the product increment; gather stakeholder feedback; adapt the backlog |
| Sprint Retrospective | Scrum Team only | Reflect on the team's process; agree on improvements for next sprint |
The signals here — "stakeholders welcome" and "demonstrating the checkout flow" — both point to a Sprint Review. Inviting stakeholders to a retrospective is an anti-pattern; it can prevent the team from speaking candidly about their working process.
4 / 25
During backlog refinement, the Product Owner presents this story:
"As a registered user, I want to reset my password so that I can regain access to my account."
The tech lead says: "This story is not ready yet." Which addition would most clearly make this story ready to enter the sprint?
The Definition of Ready (DoR) specifies what a story needs before the team can confidently pull it into a sprint. The three core requirements are:
- Acceptance criteria (Given/When/Then) — makes the story testable and prevents scope ambiguity during development
- Size estimate — without an agreed estimate, the team cannot make informed sprint planning decisions
- Dependencies identified — unresolved dependencies cause mid-sprint blockers that derail delivery
| DoR checkpoint | Why it matters |
|---|---|
| Acceptance criteria written | Team knows exactly when the story is done — no ambiguity at review |
| Story estimated by the team | Enables sprint capacity and commitment decisions |
| Dependencies flagged or resolved | Prevents mid-sprint blockers from halting delivery |
A JIRA link (Option A) and a developer assignment (Option C) are administrative details, not readiness criteria. A UI prototype (Option D) is rarely required for a story to be considered ready.
5 / 25
The Scrum Master opens sprint planning with:
"Our 6-sprint rolling average velocity is 38 story points. This sprint we have a bank holiday and one team member is out on Friday, so we are forecasting 35 points of work."
Which estimation and communication principle is being correctly applied here?
Using rolling average velocity combined with a capacity adjustment is the standard Agile forecasting approach — honest, data-backed, and transparent to stakeholders:
| Concept | Explanation |
|---|---|
| Rolling average velocity | Average of the last 3–6 sprints; smooths out outliers for more reliable forecasting |
| Capacity adjustment | Reduces the forecast proportionally when team availability is lower than usual |
| Forecast language | Modern Scrum prefers "forecast" over "commit" — it signals a plan, not a binding contract |
There is no Scrum rule requiring a 10% buffer (Option B) or prohibiting forecasts above previous velocity (Option D). Reducing the forecast to match lower availability is not deceptive (Option A) — it is honest planning that accounts for real-world constraints.
6 / 25
The key here isn't just about *what* the logging does, but *why* it's relevant to the sprint. Option A incorrectly frames logging as solely a debugging tool – while that's true in some contexts, Agile emphasizes using metrics and data to drive decisions. Option B is partially correct but doesn't connect it directly to the Sprint Goal. Option C accurately explains how monitoring API usage contributes to optimization efforts, aligning with the sprint objective of reducing latency. Option D presents a common anti-pattern – blindly removing logging without considering its potential value.
7 / 25
Sarah is updating the team on her progress during the daily standup. She says: 'I've completed the user authentication flow and am now working on the integration with the payment gateway.' Her Scrum Master asks, 'Great! Can you briefly summarize what you achieved today that contributes to the Sprint Goal of improving the onboarding experience?' Which of the following responses best reflects Sarah's role in this scenario?The core purpose of the daily standup is to provide a quick update on progress *towards* the Sprint Goal. Option 1 describes work that isn't directly related – debugging UI issues doesn't contribute to onboarding. Option 2 accurately reflects completion of a key task as described in the scenario. Options 3 and 4 are too vague, focusing on future tasks or testing without connecting back to the Sprint Goal. Therefore, option 1 is incorrect because it focuses on unrelated work.
8 / 25
During a Sprint Review, the development team demonstrates a new feature – a streamlined user profile editing interface. The Product Owner asks the team, 'How does this new functionality contribute to our Sprint Goal of increasing user engagement?' Which response best captures the purpose of the Sprint Review within an Agile/Scrum context?
Remember: Sprint Reviews are about inspecting and adapting the product based on stakeholder feedback.
This question tests understanding of the core purpose of the Sprint Review. The correct answer (option 2) highlights that the review focuses on *inspecting* the increment and *gathering feedback*, directly relating it to the Sprint Goal. Options A and B focus on individual tasks or stories rather than the overall goal, while option D misrepresents the value of a Sprint Review.
9 / 25
During a Sprint Retrospective, the team is discussing impediments. David says, 'I'm spending too much time answering emails from stakeholders – it's pulling me away from coding.' The Scrum Master asks, 'How can we address this to improve our flow?' Which of the following actions would best align with the principles of a Scrum Retrospective?
The Sprint Retrospective is about inspecting and adapting the team's processes. Option 2 correctly identifies that the team needs to understand *why* David spends so much time on emails – this root cause analysis is crucial for improving the flow. Options A and D focus solely on individual behavior without addressing the systemic issue, while option B suggests a simplistic solution that doesn't address the underlying problem.
10 / 25
Mark is explaining the Sprint Retrospective to a new team member. He says: 'We'll spend 30 minutes at the end of the sprint reflecting on what went well and what could be improved. We'll use techniques like 'Start, Stop, Continue' to identify action items.' During this retrospective, Liam suggests that the team should focus solely on technical challenges encountered during the sprint. Which statement best describes Mark's approach to facilitating the Sprint Retrospective within an Agile/Scrum framework? Consider what the primary purpose of a retrospective is.
The core purpose of a Sprint Retrospective is *not* simply to solve immediate problems. It's about inspecting and adapting the team's processes – how they work together – to improve future performance. Option 1 incorrectly suggests focusing solely on technical issues, missing the broader goal of process improvement. Options 2 accurately captures this aim; option 3 acknowledges that other feedback is valuable, but doesn't fully represent Mark's approach, and option 4 misunderstands the distinct purpose of a retrospective compared to daily stand-ups.
11 / 25
The key here isn't just about *what* the logging does, but *why* it's relevant to the sprint. Option A incorrectly frames logging as solely a debugging tool – while that's true in some contexts, Agile emphasizes using metrics and data to drive decisions. Option B is partially correct but doesn't connect it directly to the Sprint Goal. Option C accurately explains how monitoring API usage contributes to optimization efforts, aligning with the sprint objective of reducing latency. Option D presents a common anti-pattern – blindly removing logging without considering its potential value.
12 / 25
Sarah is updating the team on her progress during the daily standup. She says: 'I've completed the user authentication flow and am now working on the integration with the payment gateway.' Her Scrum Master asks, 'Great! Can you briefly summarize what you achieved today that contributes to the Sprint Goal of improving the onboarding experience?' Which of the following responses best reflects Sarah's role in this scenario?The core purpose of the daily standup is to provide a quick update on progress *towards* the Sprint Goal. Option 1 describes work that isn't directly related – debugging UI issues doesn't contribute to onboarding. Option 2 accurately reflects completion of a key task as described in the scenario. Options 3 and 4 are too vague, focusing on future tasks or testing without connecting back to the Sprint Goal. Therefore, option 1 is incorrect because it focuses on unrelated work.
13 / 25
During a Sprint Review, the development team demonstrates a new feature – a streamlined user profile editing interface. The Product Owner asks the team, 'How does this new functionality contribute to our Sprint Goal of increasing user engagement?' Which response best captures the purpose of the Sprint Review within an Agile/Scrum context?
Remember: Sprint Reviews are about inspecting and adapting the product based on stakeholder feedback.
This question tests understanding of the core purpose of the Sprint Review. The correct answer (option 2) highlights that the review focuses on *inspecting* the increment and *gathering feedback*, directly relating it to the Sprint Goal. Options A and B focus on individual tasks or stories rather than the overall goal, while option D misrepresents the value of a Sprint Review.
14 / 25
During a Sprint Retrospective, the team is discussing impediments. David says, 'I'm spending too much time answering emails from stakeholders – it's pulling me away from coding.' The Scrum Master asks, 'How can we address this to improve our flow?' Which of the following actions would best align with the principles of a Scrum Retrospective?
The Sprint Retrospective is about inspecting and adapting the team's processes. Option 2 correctly identifies that the team needs to understand *why* David spends so much time on emails – this root cause analysis is crucial for improving the flow. Options A and D focus solely on individual behavior without addressing the systemic issue, while option B suggests a simplistic solution that doesn't address the underlying problem.
15 / 25
Mark is explaining the Sprint Retrospective to a new team member. He says: 'We'll spend 30 minutes at the end of the sprint reflecting on what went well and what could be improved. We'll use techniques like 'Start, Stop, Continue' to identify action items.' During this retrospective, Liam suggests that the team should focus solely on technical challenges encountered during the sprint. Which statement best describes Mark's approach to facilitating the Sprint Retrospective within an Agile/Scrum framework? Consider what the primary purpose of a retrospective is.
The core purpose of a Sprint Retrospective is *not* simply to solve immediate problems. It's about inspecting and adapting the team's processes – how they work together – to improve future performance. Option 1 incorrectly suggests focusing solely on technical issues, missing the broader goal of process improvement. Options 2 accurately captures this aim; option 3 acknowledges that other feedback is valuable, but doesn't fully represent Mark's approach, and option 4 misunderstands the distinct purpose of a retrospective compared to daily stand-ups.
16 / 25
The key here isn't just about *what* the logging does, but *why* it's relevant to the sprint. Option A incorrectly frames logging as solely a debugging tool – while that's true in some contexts, Agile emphasizes using metrics and data to drive decisions. Option B is partially correct but doesn't connect it directly to the Sprint Goal. Option C accurately explains how monitoring API usage contributes to optimization efforts, aligning with the sprint objective of reducing latency. Option D presents a common anti-pattern – blindly removing logging without considering its potential value.
17 / 25
Sarah is updating the team on her progress during the daily standup. She says: 'I've completed the user authentication flow and am now working on the integration with the payment gateway.' Her Scrum Master asks, 'Great! Can you briefly summarize what you achieved today that contributes to the Sprint Goal of improving the onboarding experience?' Which of the following responses best reflects Sarah's role in this scenario?The core purpose of the daily standup is to provide a quick update on progress *towards* the Sprint Goal. Option 1 describes work that isn't directly related – debugging UI issues doesn't contribute to onboarding. Option 2 accurately reflects completion of a key task as described in the scenario. Options 3 and 4 are too vague, focusing on future tasks or testing without connecting back to the Sprint Goal. Therefore, option 1 is incorrect because it focuses on unrelated work.
18 / 25
During a Sprint Review, the development team demonstrates a new feature – a streamlined user profile editing interface. The Product Owner asks the team, 'How does this new functionality contribute to our Sprint Goal of increasing user engagement?' Which response best captures the purpose of the Sprint Review within an Agile/Scrum context?
Remember: Sprint Reviews are about inspecting and adapting the product based on stakeholder feedback.
This question tests understanding of the core purpose of the Sprint Review. The correct answer (option 2) highlights that the review focuses on *inspecting* the increment and *gathering feedback*, directly relating it to the Sprint Goal. Options A and B focus on individual tasks or stories rather than the overall goal, while option D misrepresents the value of a Sprint Review.
19 / 25
During a Sprint Retrospective, the team is discussing impediments. David says, 'I'm spending too much time answering emails from stakeholders – it's pulling me away from coding.' The Scrum Master asks, 'How can we address this to improve our flow?' Which of the following actions would best align with the principles of a Scrum Retrospective?
The Sprint Retrospective is about inspecting and adapting the team's processes. Option 2 correctly identifies that the team needs to understand *why* David spends so much time on emails – this root cause analysis is crucial for improving the flow. Options A and D focus solely on individual behavior without addressing the systemic issue, while option B suggests a simplistic solution that doesn't address the underlying problem.
20 / 25
Mark is explaining the Sprint Retrospective to a new team member. He says: 'We'll spend 30 minutes at the end of the sprint reflecting on what went well and what could be improved. We'll use techniques like 'Start, Stop, Continue' to identify action items.' During this retrospective, Liam suggests that the team should focus solely on technical challenges encountered during the sprint. Which statement best describes Mark's approach to facilitating the Sprint Retrospective within an Agile/Scrum framework? Consider what the primary purpose of a retrospective is.
The core purpose of a Sprint Retrospective is *not* simply to solve immediate problems. It's about inspecting and adapting the team's processes – how they work together – to improve future performance. Option 1 incorrectly suggests focusing solely on technical issues, missing the broader goal of process improvement. Options 2 accurately captures this aim; option 3 acknowledges that other feedback is valuable, but doesn't fully represent Mark's approach, and option 4 misunderstands the distinct purpose of a retrospective compared to daily stand-ups.
21 / 25
The key here isn't just about *what* the logging does, but *why* it's relevant to the sprint. Option A incorrectly frames logging as solely a debugging tool – while that's true in some contexts, Agile emphasizes using metrics and data to drive decisions. Option B is partially correct but doesn't connect it directly to the Sprint Goal. Option C accurately explains how monitoring API usage contributes to optimization efforts, aligning with the sprint objective of reducing latency. Option D presents a common anti-pattern – blindly removing logging without considering its potential value.
22 / 25
Sarah is updating the team on her progress during the daily standup. She says: 'I've completed the user authentication flow and am now working on the integration with the payment gateway.' Her Scrum Master asks, 'Great! Can you briefly summarize what you achieved today that contributes to the Sprint Goal of improving the onboarding experience?' Which of the following responses best reflects Sarah's role in this scenario?The core purpose of the daily standup is to provide a quick update on progress *towards* the Sprint Goal. Option 1 describes work that isn't directly related – debugging UI issues doesn't contribute to onboarding. Option 2 accurately reflects completion of a key task as described in the scenario. Options 3 and 4 are too vague, focusing on future tasks or testing without connecting back to the Sprint Goal. Therefore, option 1 is incorrect because it focuses on unrelated work.
23 / 25
During a Sprint Review, the development team demonstrates a new feature – a streamlined user profile editing interface. The Product Owner asks the team, 'How does this new functionality contribute to our Sprint Goal of increasing user engagement?' Which response best captures the purpose of the Sprint Review within an Agile/Scrum context?
Remember: Sprint Reviews are about inspecting and adapting the product based on stakeholder feedback.
This question tests understanding of the core purpose of the Sprint Review. The correct answer (option 2) highlights that the review focuses on *inspecting* the increment and *gathering feedback*, directly relating it to the Sprint Goal. Options A and B focus on individual tasks or stories rather than the overall goal, while option D misrepresents the value of a Sprint Review.
24 / 25
During a Sprint Retrospective, the team is discussing impediments. David says, 'I'm spending too much time answering emails from stakeholders – it's pulling me away from coding.' The Scrum Master asks, 'How can we address this to improve our flow?' Which of the following actions would best align with the principles of a Scrum Retrospective?
The Sprint Retrospective is about inspecting and adapting the team's processes. Option 2 correctly identifies that the team needs to understand *why* David spends so much time on emails – this root cause analysis is crucial for improving the flow. Options A and D focus solely on individual behavior without addressing the systemic issue, while option B suggests a simplistic solution that doesn't address the underlying problem.
25 / 25
Mark is explaining the Sprint Retrospective to a new team member. He says: 'We'll spend 30 minutes at the end of the sprint reflecting on what went well and what could be improved. We'll use techniques like 'Start, Stop, Continue' to identify action items.' During this retrospective, Liam suggests that the team should focus solely on technical challenges encountered during the sprint. Which statement best describes Mark's approach to facilitating the Sprint Retrospective within an Agile/Scrum framework? Consider what the primary purpose of a retrospective is.
The core purpose of a Sprint Retrospective is *not* simply to solve immediate problems. It's about inspecting and adapting the team's processes – how they work together – to improve future performance. Option 1 incorrectly suggests focusing solely on technical issues, missing the broader goal of process improvement. Options 2 accurately captures this aim; option 3 acknowledges that other feedback is valuable, but doesn't fully represent Mark's approach, and option 4 misunderstands the distinct purpose of a retrospective compared to daily stand-ups.
Frequently Asked Questions
What will I practice in "Scrum Ceremonies Vocabulary | Agile & Scrum Exercises"?
This is an Agile & Scrum exercise set. It walks through 25 scenario-based multiple-choice questions built around real usage of Agile & Scrum terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 25 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the Agile & Scrum vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Agile & Scrum exercises?
See the Agile & Scrum exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — Agile & Scrum vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.