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.
Do You Have Questions Or Are You 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 of one to four weeks duration. The sprint is the heartbeat of Scrum, creating rhythm and allowing for rapid feedback.
Implementing Scrum effectively requires that the following elements are clearly established and maintained.
The Scrum Team
The fundamental unit of Scrum is a small, self-managing, cross-functional team with three accountabilities, often referred to as the three Scrum roles.
Developers — (3-8) individuals with different skills, who collaboratively create a valuable increment each sprint.
Product Owner — (1) the voice of the business; the PO 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 and personal growth.
A note on scaling: If the team grows too large the members should reorganize into multiple cohesive teams, each focused on the same product. Therefore, they should share the same product goal, product backlog, and product owner.
Scrum Commitments
Clear purpose directs the work and makes the intent visible to all.
Product Goal — describes a future state of the product: a commitment to clear direction.
Sprint Goal — a concrete stepping stone towards 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 one is reviewed regularly at one or more of the Scrum Events.
Product Backlog — an evolving, ordered list of items, committed to the product goal; this backlog is 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
There are three sprint events, one daily event, and a meta-event containing the other four. These events allow inspection and adaptation to occur on a regular basis, at different levels of granularity.
Sprint — a time-boxed container for the work and the four alignment events; the heartbeat of Scrum, where ideas are turned into value.
Sprint Planning — occurs at the start of every sprint: product owner and developers define the sprint goal and select backlog items; developers may create a list of tasks.
Daily Scrum — occurs every working day, ideally at the same time and place: a short developer conversation to inspect/adapt the sprint backlog in service to sprint goal.
Sprint Review — occurs at the end of every sprint: stakeholders inspect the increment, and offer feedback; the scrum team may update the product backlog.
Sprint Retrospective — occurs immediately after the sprint review: the scrum team reflects on the sprint and identifies changes to improve its 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).
The latest update to the source document — and synced on this page — was on June 21, 2025.
The original document was initially released on March 21, 2025.
You can view the changes from V1 to V2 here if you are interested.
Much discussion ensued over these small changes heh. Enjoy it!
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.
This page last updated by Michael Vizdos on June 21, 2025.