The Developers dislike going round the room each morning and propose replacing it with a five-minute walk of the Sprint Backlog board, discussing only the items that put the Sprint Goal at risk. They ask the Scrum Master whether that is still Scrum.
Professional Scrum Master I, objective 1. Understanding and applying the Scrum framework hard
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
The options
Correct Yes — the Developers may select whatever structure and techniques they want, provided the Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day
Correct. Scrum names the purpose and the timebox and then deliberately leaves the format to the people doing the work, because choosing their own structure is part of what self-management means.
Not correct No — each Developer must state what they did, what they will do next and what is blocking them
Wrong. Those three questions are a technique many teams use and the 2020 framework does not require them. A team can answer all three perfectly and still hold a Daily Scrum that inspects nothing about the Sprint Goal.
Not correct Yes, but only if the event still occupies the full fifteen minutes
Wrong. Fifteen minutes is a maximum. An event that achieves its purpose in five minutes has achieved its purpose.
Not correct No — changing the format means the event is no longer a formal inspection, so the Sprint Backlog may not be adapted that day
Wrong on both halves. The format does not determine whether inspection happened, and the Daily Scrum is not the only time Developers may adjust their plan — they often meet through the day to re-plan the rest of the Sprint's work.
Why
Scrum specifies the Daily Scrum's purpose, its timebox, who it is for and how often it happens, and then stops. Two outputs decide whether it worked: focus on progress toward the Sprint Goal, and an actionable plan for the next day of work. A format that produces those is a good Daily Scrum, however unfamiliar it looks; a format that produces neither is a bad one, however closely it follows a remembered script.
Where this comes from
- Cited
- Scrum Guide section Daily Scrum
- What it says
- The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.
Practise this
Reading one question is not practice. The trainer will draw a set from objective 1 and space the ones you get wrong.
Practise Professional Scrum Master I
More questions on this objective
- A department is choosing an approach for a product where both the requirements and the technology are poorly understood and keep changing as the team learns. Someone argues for Scrum "because it is founded on empiricism". What does founding an approach on empiricism actually commit the team to? machine-checked
- At the end of a Sprint three items are functionally complete but have not been through the automated test suite the Definition of Done requires. To avoid an awkward conversation the Developers mark them Done on the board and include them in the Sprint Review. Which pillar has been damaged, and what follows from that? machine-checked
- A Scrum Team holds every event on schedule, keeps a burn-down chart and reviews its metrics carefully. For six Sprints running, the same impediment — a two-day wait for a shared test environment — has been named in the Retrospective, and nothing about it has changed. What is the accurate diagnosis? machine-checked
- Mid-Sprint, the Developers discover that a third-party API rate-limits far below what they assumed, which makes the current plan unworkable. One of them suggests carrying on as planned and raising it at the Sprint Retrospective, so the Sprint is not disrupted. What should happen instead? machine-checked
- Which THREE of these statements about Scrum theory are accurate as the framework defines it? machine-checked
- A Developer is fairly sure the design the team agreed last week will not scale. The team is halfway through the Sprint, everyone else seems content, and saying so means an uncomfortable conversation and probably rework. Which Scrum value most directly asks them to speak? machine-checked
All questions on Understanding and applying the Scrum framework