Simple Guide To Scrum

The version of "A Simple Guide To Scrum" you are reading now is enhanced with direct links to the 2020 Scrum Guide references published in the Interactive Scrum Guide by Michael Vizdos (creator of ImplementingScrum.com and the Scrum Guide YouTube Video Playlist and the Implementing Scrum - Unscripted Podcast).

Please also consider paying a small fee for the Enhanced Scrum Guide.

Have questions or interested in learning more? Please contact me (Michael Vizdos) and subscribe to receive FREE Scrum Cartoons every Saturday morning.

Scrum Definition

Scrum is a lightweight, team-centric framework for solving complex problems and generating value. Purposefully incomplete, Scrum is designed to be built upon by the collective intelligence of the people using it.

Founded on empiricism and lean thinking, Scrum enables teams to work artfully, adapting to changing requirements while generating value for the user, early and often. For this to be successful, those Implementing Scrum need to work with focus, and embody certain values, including but not limited to commitment, openness, respect and courage.

Work is done in short cycles known as "sprints," typically one to four weeks. The sprint is the heartbeat of Scrum, creating rhythm and allowing for rapid feedback.

The Scrum Team

The fundamental unit of Scrum is a small, self-managing, cross-functional team with three accountabilities:

• Developers — (3-8) individuals with different skills, who collaboratively create a valuable increment each sprint.
• Product Owner — (1) the voice of the business; maximizes product value by talking with customers, setting clear product goals, and managing the product backlog.
• Scrum Master — (1) organizational change agent; ensures Scrum is applied effectively and fosters an environment for continuous learning.

A note on scaling: if the team grows too large, members should reorganize into multiple cohesive teams, each focused on the same product — sharing the same product goal, product backlog, and product owner.

Scrum Commitments

Clear purpose directs the work and makes intent visible to all.

• Product Goal — describes a future state of the product: a commitment to clear direction.
• Sprint Goal — a concrete stepping stone toward the product goal: a commitment to incremental value.
• Definition of Done — a commitment to quality for all work items.

Scrum Artifacts

These elements provide transparency. Each is reviewed regularly at one or more of the Scrum Events.

• Product Backlog — an evolving, ordered list of items, committed to the product goal; regularly refined and updated.
• Sprint Backlog — selected product backlog items and a plan of action committed to the sprint goal.
• Increment — completed backlog items that actualize the sprint goal and meet an agreed definition of done.

Scrum Events

Three sprint events, one daily event, and a meta-event containing the other four — allowing inspection and adaptation at different levels of granularity.

• Sprint — a time-boxed container for the work and the four alignment events; the heartbeat of Scrum.
• Sprint Planning — start of every sprint: Product Owner and Developers define the sprint goal and select backlog items.
• Daily Scrum — every working day: a short Developer conversation to inspect/adapt the sprint backlog in service of the sprint goal.
• Sprint Review — end of every sprint: stakeholders inspect the increment and offer feedback.
• Sprint Retrospective — immediately after the Sprint Review: the Scrum Team reflects and identifies changes to improve effectiveness.

End Note

Scrum is a container for agility, inviting in other techniques, methodologies, and practices. The Scrum framework, adopted holistically, enables teams to inspect, adapt, and deliver valuable products in complex environments.

Reference Information

Small modifications — including embedded links for your reference — have been made from the original work at "A Simple Guide To Scrum" (of which Michael Vizdos was a contributor and collaborator). This work is in compliance with the Attribution Share-Alike license of Creative Commons, established by the official Scrum Guide, 2020, and the Interactive Scrum Guide by Michael Vizdos. You are free to utilize the content in any way you like, but are advised to read the original Scrum Guide Creative Commons agreement, and honor the same.