Domain 1 of 3

Understanding and Applying the Scrum Framework

Empiricism and the Scrum Values, the three accountabilities, the five events with their timeboxes and the three artifacts with their commitments.

15
Concepts
~35%
Of the exam
37
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 TeamOne team of ten or fewer people, with three accountabilities and no sub-teams or hierarchies, responsible for all product-related activities.03The 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.04The SprintA fixed-length event of one month or less that contains all the other events, and the container in which ideas turn into value.05Sprint PlanningThe event that starts a Sprint, timeboxed to a maximum of eight hours for a one-month Sprint, addressing three topics.06The 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.07The 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.08The 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.09Timeboxes in ScrumThe maximum durations Scrum places on the Sprint and its events, and the reason each limit is set where it is.10Cancelling a SprintA Sprint may be cancelled when its Sprint Goal becomes obsolete, and only the Product Owner has the authority to do it.11The Product BacklogAn emergent, ordered list of what is needed to improve the product, and the single source of work undertaken by the Scrum Team.12The 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.13The IncrementA concrete stepping stone toward the Product Goal, additive to all prior Increments and verified to work together with them.14The Sprint GoalThe single objective for one Sprint, the Sprint Backlog's commitment, and the only thing in a Sprint the Developers actually promise.15The Definition of DoneThe shared standard for what "finished" means, a commitment to the Increment, and the thing that stops undone work accumulating invisibly.
Try a question from this domain

Which three pillars uphold empirical process control in Scrum?

  • APlanning, execution and review
  • BTransparency, inspection and adaptation
  • CCommitment, focus and courage
  • DEstimation, measurement and reporting
37 questions on this domain.

One per page, with a worked explanation.

Start the set