The Scrum Guide (In under 15 minutes!)

Scrum, developed by Ken Schwaber and Jeff Sutherland in the early 1990s, is a lightweight framework designed to help teams solve complex problems and generate value. The official Scrum Guide, first published in 2010 and updated in 2020, outlines its roles, events, artifacts, and rules. Scrum is founded on empiricism, relying on real-world experience and observation, and lean thinking, which focuses on reducing waste. It operates through the empirical pillars of transparency, inspection, and adaptation.

Scrum's effectiveness relies on five core values: commitment to goals and mutual support, focus on sprint work for optimal progress, openness about work and challenges, respect for team members as capable individuals, and courage to tackle difficult problems. Adhering to these values fosters trust and brings the empirical pillars of transparency, inspection, and adaptation to life.

A Scrum Team consists of three roles: a Scrum Master, a Product Owner, and Team Members, with no hierarchy. These teams are cross-functional, possessing all necessary skills, and self-managing, deciding internally how to achieve their work. They are typically 10 or fewer people to maintain agility. Team Members are accountable for sprint planning, ensuring quality, adapting plans, and holding each other accountable. The Product Owner maximizes the value of the team's work, managing the product backlog and defining the product goal. The Scrum Master establishes and defends the Scrum process, coaching the team, removing impediments, and ensuring events are productive.

Scrum involves five events, with the 'Sprint' as the container for all others. These events foster transparency, inspection, and adaptation. Sprints are fixed-length timeboxes, usually two weeks, where a new sprint begins immediately after the old one. During a sprint, the team works towards a 'Sprint Goal'. Sprint Planning initiates the sprint, collaboratively defining its purpose, selecting product backlog items, and planning how to achieve them, resulting in the 'Sprint Backlog'. The Daily Scrum is a brief, 15-minute daily meeting for the team to inspect progress towards the sprint goal and adapt their plan. The Sprint Review (showcase) is held to inspect the sprint's outcome with stakeholders and adapt the product backlog. The Sprint Retrospective (retro) allows the team to reflect on their process and identify improvements for future sprints.

Scrum utilizes three artifacts to maximize transparency: the 'Product Backlog', the 'Sprint Backlog', and the 'Increment'. The Product Backlog is an ordered list of what is needed to improve the product, with the 'Product Goal' acting as its long-term objective. The Sprint Backlog is composed of the 'Sprint Goal', selected product backlog items, and an actionable plan for delivering the 'Increment'. The Increment is a concrete, usable stepping stone towards the product goal. The 'Definition of Done' ensures transparency by clearly defining when work is completed and meets quality standards, making it part of an increment.