The vocabulary the exams and the daily work both assume you already have. Every entry gives the definition, the source it is drawn from, and the misreadings that follow from getting it wrong.
38 concepts in Scrum, page 1 of 2
A Sprint may be cancelled when its Sprint Goal becomes obsolete, and only the Product Owner has the authority to do it.
Scrum
Six 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.
Scrum
The Scrum Team holds every skill needed to create value each Sprint, without depending on people outside the team.
Scrum
One 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.
Scrum
Scrum is founded on empiricism and lean thinking. Transparency, inspection and adaptation are the pillars that make empiricism work.
Scrum
Scrum asks that Product Backlog items carry a size, says who is responsible for it, and names no technique for arriving at one.
Scrum
Scrum prescribes no forecasting technique. What it defines is that the Sprint Goal is the commitment, and that projections come from observation.
Scrum
Facilitation carries the process while the group keeps the content, which is what separates helping an event reach its purpose from chairing it.
Scrum
The word conflict appears nowhere in the 2020 Scrum Guide, so the material comes from team research, and the one boundary the framework does draw is that the Scrum Master never decides for the team.
Scrum
A true leader who serves the Scrum Team, the Product Owner and the organisation, and is accountable for the Scrum Team's effectiveness.
Scrum
Value is established by evidence rather than assertion, and the Increment is what makes it inspectable.
Scrum
Order expresses strategy, not preference, and being accountable for it is not the same as doing the work.
Scrum
What an entry on the Product Backlog is, what Scrum requires of it, and how much of what teams do to items comes from practices outside the framework.
Scrum
The ongoing activity of breaking down and further defining Product Backlog items into smaller, more precise items. It is not an event.
Scrum
A product is a vehicle to deliver value with a clear boundary, known stakeholders and well-defined users or customers.
Scrum
When a Done Increment can reach users, why the Sprint Review is not a gate, and what a rare batched release does to the feedback loop.
Scrum
More teams on one product changes nothing about what a product is. One Product Owner, one Product Backlog, one Product Goal and one Increment survive the scaling, and dependencies become the work.
Scrum
The 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.
Scrum
The event that starts a Sprint, timeboxed to a maximum of eight hours for a one-month Sprint, addressing three topics.
Scrum
How stakeholders participate in Scrum, where their input enters, and where the Product Owner's decision stands.
Scrum