Scrum states a short list of things the Developers are always accountable for, whatever the domain of work. Which THREE of these are on it?
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
Choose 3.
Correct Creating a plan for the Sprint, the Sprint Backlog
Correct. The Sprint Backlog is the Developers' plan, created by them and updated by them, which is why nobody else may hand it over ready-made.
Correct Instilling quality by adhering to a Definition of Done
Correct. Quality is not a phase or a separate team's job in Scrum: the Developers are required to conform to the Definition of Done, every Sprint.
Correct Adapting their plan each day toward the Sprint Goal
Correct. This is what the Daily Scrum exists to serve, and it is why the plan is expected to change during the Sprint rather than after it.
Not correct Ordering the Product Backlog so that the most valuable work is at the top
Wrong. Ordering Product Backlog items is one of the four things Scrum places with the Product Owner. Developers influence it by explaining cost and trade-offs, not by re-ordering it.
Not correct Ensuring that every Sprint Review ends with an Increment released to customers
Wrong. An Increment may be released before the Sprint Review or after it, and the Sprint Review is never a gate to releasing value. Whether to release is a value decision, and value decisions belong to the Product Owner.
Why
The list has a fourth entry worth knowing even though it is not offered here — holding each other accountable as professionals — and its presence tells you what kind of list this is. Every item is about how the Developers govern their own work: their plan, their quality bar, their daily adaptation, their conduct with each other. Anything about what the product should do next belongs to the Product Owner instead.
Where this comes from
- Cited
- Scrum Guide section Developers
- What it says
- Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
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