The Definition of Done for a payments product requires penetration testing and updated operator documentation. The Developers forecast each Sprint on build effort alone, treating those two as "the checklist we run at the end". For four Sprints running, two or three items have finished the Sprint undocumented and untested. What does Scrum expect at Sprint Planning?
Professional Scrum Master I, objective 1. Understanding and applying the Scrum framework medium
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
Not correct Ask the Product Owner to trim the Definition of Done so that the forecast and the standard match
Wrong twice. The Definition of Done is not the Product Owner's to trim, and lowering a payments product's quality bar to protect a forecast is the trade Scrum rules out by saying quality does not decrease.
Correct For each selected item the Developers plan the work needed to create an Increment that meets the Definition of Done — so the testing and documentation are inside the forecast, not after it
Correct. The third topic of Sprint Planning is explicit that the plan targets an Increment meeting the Definition of Done, which makes that work part of what the Developers are selecting, not a tail that follows the selection.
Not correct Add a stabilisation Sprint every fourth Sprint in which the outstanding testing and documentation are cleared
Wrong, and there is no such thing in Scrum. A Sprint that produces no usable Increment is a symptom of a Definition of Done nobody is planning against, and scheduling it makes the shortfall permanent.
Not correct Keep the current forecast and mark items Done when the build is complete, finishing the Definition of Done work early in the next Sprint
Wrong, and it is the practice most teams in this position actually adopt. Work that does not meet the Definition of Done is not part of the Increment at all; the item returns to the Product Backlog, and calling it Done makes the board lie.
Why
The Definition of Done is an input to planning, not an inspection at the end of the Sprint. Scrum wires it in at two points: the Developers plan the work necessary to create an Increment that meets it, and their confidence in a forecast grows with what they know about past performance, upcoming capacity and the Definition of Done itself. A team that forecasts on build effort alone is forecasting something other than Done work, which is why the gap reappears every Sprint.
Where this comes from
- Cited
- Scrum Guide section Topic Three: How will the chosen work get done?
- What it says
- For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done.
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