Domain 1 of 5

Scrum Foundations

Scrum theory and the five scrum values, the scrum team, the events with their timeboxes and the three artifacts with their commitments. Scrum Alliance requires every trainer to cover these objectives before or during the CSPO course.

Concepts

~20%

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.04Self-managementThe Scrum Team decides who does what, when and how, and the Scrum Master's job is to make that possible rather than to direct it.05Cross-functionalityThe Scrum Team holds every skill needed to create value each Sprint, without depending on people outside the team.06How 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.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 IncrementA concrete stepping stone toward the Product Goal, additive to all prior Increments and verified to work together with them.10The Definition of DoneThe shared standard for what "finished" means, a commitment to the Increment, and the thing that stops undone work accumulating invisibly.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 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.13The 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.14The 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.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 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.17Timeboxes in ScrumThe maximum durations Scrum places on the Sprint and its events, and the reason each limit is set where it is.

Try a question from this domain

Three Sprints into a new product, usage data shows that the feature the team has been building for six weeks is opened by four per cent of users. The Product Owner suggests carrying on because the work is nearly finished and stopping now would waste the effort so far. Which response is most consistent with empiricism?

AFinish the feature, because abandoning nearly complete work wastes the investment already made.
BAdapt the Product Backlog now on the basis of what has been observed, and treat the six weeks as already spent regardless of the decision.
CContinue for one more Sprint and decide at the Sprint Review after that.
DEscalate to the sponsor who requested the feature and follow their decision.

24 questions on this domain.

One per page, with a worked explanation.

Start the set