Which THREE of these does the Sprint Retrospective inspect, as Scrum describes the event?
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
Choose 3.
Correct How the last Sprint went with regard to individuals and interactions
Correct. Individuals and interactions are named explicitly, which is what makes the Retrospective a conversation about people and not only about process.
Correct The processes and tools the Scrum Team used
Correct. Tooling is in scope: a two-day wait for a shared environment is exactly the kind of thing the event exists to surface and then remove.
Correct The Definition of Done
Correct, and it is the one people miss. The Retrospective is where the team asks whether its quality bar is still right for the product — which is why the Definition of Done is not renegotiated during Sprint Planning.
Not correct The ordering of the Product Backlog
Wrong event. Product Backlog ordering is the Product Owner's decision, informed by what stakeholders say at the Sprint Review. The Retrospective inspects how the team works, not what the product should do next.
Not correct Whether each Developer met their individual performance objectives
Wrong. Scrum sets no individual objectives and inspects none. Introducing them turns an event that depends on candour into one where nobody can afford to name a mistake.
Why
The Retrospective inspects how the last Sprint went with regard to individuals, interactions, processes, tools and the Definition of Done, and Scrum adds a step teams often skip: identifying the assumptions that led them astray and exploring where those assumptions came from. Cause, not just symptom. The Definition of Done sitting on that list is the detail worth carrying into the exam.
Where this comes from
- Cited
- Scrum Guide section Sprint Retrospective
- What it says
- The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their 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