Domain 1 of 3

Understanding and Applying the Scrum Framework

Empiricism and the values underneath the framework, the three accountabilities and what each one owns, the five events with their timeboxes, the three artifacts with their commitments, and the two places candidates most often lose marks, which are the Definition of Done against acceptance criteria and the practices teams adopt that the Guide does not describe.

Concepts

~50%

Of the exam

Practice questions

Concepts in this domain

01Empiricism and the three pillarsScrum is founded on empiricism and lean thinking. Transparency, inspection and adaptation are the pillars that make empiricism work.02The Scrum ValuesCommitment, Focus, Openness, Respect and Courage, the five values that make the three empirical pillars work in practice.03The Scrum TeamOne team of ten or fewer people, with three accountabilities and no sub-teams or hierarchies, responsible for all product-related activities.04How the Scrum Master servesA true leader who serves the Scrum Team, the Product Owner and the organisation, and is accountable for the Scrum Team's effectiveness.05The Product Owner accountabilityOne person, accountable for maximising the value of the product resulting from the work of the Scrum Team, and for effective Product Backlog management.06The DevelopersThe people in the Scrum Team committed to creating any aspect of a usable Increment each Sprint, defined by that commitment rather than by job title.07The SprintA fixed-length event of one month or less that contains all the other events, and the container in which ideas turn into value.08Sprint PlanningThe event that starts a Sprint, timeboxed to a maximum of eight hours for a one-month Sprint, addressing three topics.09The Daily ScrumA 15 minute event held every working day of the Sprint, in which the Developers inspect progress towards the Sprint Goal and produce an actionable plan for the next day of work.10The Sprint ReviewThe second to last event of a Sprint, in which the Scrum Team and its key stakeholders inspect what was built, discuss progress towards the Product Goal, and decide together what to do next.11The Sprint RetrospectiveThe event that concludes the Sprint, in which the Scrum Team inspects how it worked and identifies the changes that would make the next Sprint more effective.12Timeboxes in ScrumThe maximum durations Scrum places on the Sprint and its events, and the reason each limit is set where it is.13Cancelling a SprintA Sprint may be cancelled when its Sprint Goal becomes obsolete, and only the Product Owner has the authority to do it.14The Product BacklogAn emergent, ordered list of what is needed to improve the product, and the single source of work undertaken by the Scrum Team.15The Sprint BacklogThe Developers' plan for one Sprint, made of the Sprint Goal, the items selected to reach it and an actionable plan for delivering the Increment.16The IncrementA concrete stepping stone toward the Product Goal, additive to all prior Increments and verified to work together with them.17The Sprint GoalThe single objective for one Sprint, the Sprint Backlog's commitment, and the only thing in a Sprint the Developers actually promise.18The Definition of DoneThe shared standard for what "finished" means, a commitment to the Increment, and the thing that stops undone work accumulating invisibly.19Definition of Done and Acceptance Criteria in ScrumOne standard applies to the whole Increment and the other to a single Product Backlog item, so an item can satisfy its acceptance criteria and still fail the Definition of Done.20Common Scrum Anti Patterns and What the Scrum Guide SaysSix practices that spread easily and quietly move a decision away from the accountability that owns it, each paired with the sentence in the 2020 Scrum Guide that settles them.

Try a question from this domain

A payments API team ends every Sprint Review with the stakeholders' concerns written into the Scrum Master's notes, and the Product Backlog looks the same the next morning as it did the day before. Which pillar is failing, and what should follow?

ATransparency, so the notes should be circulated to everyone who attended.
BInspection, so the review needs longer to reach every item in the Sprint.
CAdaptation, so the Product Backlog should change on what the review found.
DNothing is failing, since recording the concerns is the event's own output.

53 questions on this domain.

One per page, with a worked explanation.

Start the set