Essential Scrum
About this book
A comprehensive reference on Scrum covering roles, activities, artefacts and the principles beneath them, written for people who need the whole picture rather than a quick start. Rubin covers requirements at every level from product down to sprint backlog, technical debt, definition of done, estimation and velocity, release planning, and portfolio planning across multiple products. Heavily illustrated and organised so chapters stand alone as references.
Description via Product Digest.
Topics
Related concepts
- Ordering the Product BacklogOrder expresses strategy, not preference, and being accountable for it is not the same as doing the work.
- How 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.
- The IncrementA concrete stepping stone toward the Product Goal, additive to all prior Increments and verified to work together with them.
- The Product BacklogAn emergent, ordered list of what is needed to improve the product, and the single source of work undertaken by the Scrum Team.
- The SprintA fixed-length event of one month or less that contains all the other events, and the container in which ideas turn into value.
- The Sprint GoalThe single objective for one Sprint, the Sprint Backlog's commitment, and the only thing in a Sprint the Developers actually promise.
- The 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.
- The Definition of DoneThe shared standard for what "finished" means, a commitment to the Increment, and the thing that stops undone work accumulating invisibly.
- Iterative and incremental deliveryA fixed cadence, a variable scope and a usable result at the end of every cycle, together with the events that make the loop work and the reason each of them is timeboxed.
- Cancelling a SprintA Sprint may be cancelled when its Sprint Goal becomes obsolete, and only the Product Owner has the authority to do it.
- The 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.
- Timeboxes in ScrumThe maximum durations Scrum places on the Sprint and its events, and the reason each limit is set where it is.
- The Scrum TeamOne team of ten or fewer people, with three accountabilities and no sub-teams or hierarchies, responsible for all product-related activities.
- Definition 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.
- Common 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.
- Empiricism and the three pillarsScrum is founded on empiricism and lean thinking. Transparency, inspection and adaptation are the pillars that make empiricism work.
- The 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.
- The 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.