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 2 of 2
The accumulated cost of past choices that makes changing a product slower, and the Product Owner decision about when to pay it down.
Scrum
A 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.
Scrum
The shared standard for what "finished" means, a commitment to the Increment, and the thing that stops undone work accumulating invisibly.
Scrum
The 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.
Scrum
A concrete stepping stone toward the Product Goal, additive to all prior Increments and verified to work together with them.
Scrum
An emergent, ordered list of what is needed to improve the product, and the single source of work undertaken by the Scrum Team.
Scrum
The single objective the Scrum Team plans against, and why a team holding three goals is holding none.
Scrum
One person, accountable for maximising the value of the product resulting from the work of the Scrum Team, and for effective Product Backlog management.
Scrum
The accountability is fixed, but the organisation around it is not. How reporting lines, funding models and team counts change what a product owner can actually decide.
Scrum
Scrum moves three decisions away from management, which is why an adoption can look complete at the team level and fail above it, and why the Scrum Master accountability reaches further than its authority.
Scrum
One team of ten or fewer people, with three accountabilities and no sub-teams or hierarchies, responsible for all product-related activities.
Scrum
Commitment, Focus, Openness, Respect and Courage, the five values that make the three empirical pillars work in practice.
Scrum
A fixed-length event of one month or less that contains all the other events, and the container in which ideas turn into value.
Scrum
The Developers' plan for one Sprint, made of the Sprint Goal, the items selected to reach it and an actionable plan for delivering the Increment.
Scrum
The single objective for one Sprint, the Sprint Backlog's commitment, and the only thing in a Sprint the Developers actually promise.
Scrum
The 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.
Scrum
The 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.
Scrum
The maximum durations Scrum places on the Sprint and its events, and the reason each limit is set where it is.
Scrum