Every working day, the Developers on a home-robot company's firmware team hold a short, focused meeting to check how close they are to the Sprint Goal and adjust their plan for the day ahead. What Scrum event does this describe?
Select an answer to reveal the explanation.
Short Explanation
Checking in daily to see how close you are to the finish line and adjusting course — that's the whole point of the Daily Scrum. It's a short inspect-and-adapt loop aimed squarely at the Sprint Goal, held every working day of the Sprint. Nothing about looking at the team's own working process or the product itself belongs in this particular event.
Full Explanation
The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. It happens every working day of the Sprint, at the same time and place to reduce complexity, and its entire focus is the immediate plan for reaching the Sprint Goal - not a broader look at the product or the team's process. A Sprint Review is a much longer, end-of-Sprint event where the Scrum Team and stakeholders inspect the outcome of the Sprint and the state of the Product Backlog, not a daily check-in. Backlog refinement is an ongoing activity of adding detail and estimates to Product Backlog items; it isn't tied to a daily cadence or to Sprint Goal progress specifically. The Sprint Retrospective also happens once per Sprint, near the end, and inspects how the Scrum Team worked together, not daily progress toward the goal. Caveat: the Daily Scrum's format isn't prescribed by the Guide - teams can run it however works for them, as long as it stays focused on progress toward the Sprint Goal. Operational check: if a daily meeting regularly turns into detailed problem-solving or backlog grooming, that's a sign it's drifted from the Daily Scrum's actual purpose.