Scrum Guide: Audio Book - Free Audio Course

Explore empirical process control and empiricism, where knowledge comes from experience to guide decisions, scrum uses iterative, incremental cycles through transparency, inspection, and adaptation to boost predictability and control risk.

The Scrum team, with a product owner, development team, and Scrum Master, is self-organizing and cross-functional, delivering work iteratively and incrementally to maximize feedback.

The development team delivers a potentially releasable increment at the end of each sprint, with self-organizing, cross-functional members empowered to manage their own work, accountable as a team.

Keep the development team size small enough to stay nimble yet large enough to complete significant work within a sprint, balancing interaction, productivity gains, and skill requirements.

The scrum master promotes and supports scrum as defined in the scrum guide, serving as a servant leader who helps the team and its stakeholders optimize interactions to maximize value.

Explore the sprint, a time-boxed cycle of up to one month delivering a potentially releasable product increment through planning, daily scrums, development work, reviews, and retrospectives toward a sprint goal.

The product owner can cancel a sprint before the time box ends, especially if the sprint goal becomes obsolete due to company direction or market changes, with incomplete items reactivated.

Sprint planning unites the scrum team to decide what can be delivered in upcoming increment and how it will be achieved within the eight-hour time box for a one-month sprint.

Set a sprint goal that guides the development team through backlog and delivers a coherent increment, allowing flexible functionality; if needed, the team negotiates the scope with the product owner.

Foster artifact transparency to optimize value and control risk by basing decisions on the perceived state of artifacts and guiding the team with inspection and pattern sensing.

Scrum is free in this guide, with immutable roles, events, artifacts, and rules. Implementing only parts of Scrum does not make it Scrum; it exists in its entirety.

Acknowledges thousands who contributed to scrum and highlights early collaborators like Jeff Sutherland, Jeff McKenna, John scum, and Ken Schwimmer with Mike Smith and Chris Martin, whose work refined scrum.