Scrum
Scrum is a specific agile framework structured around time-boxed sprints (typically 1 to 4 weeks), three defined roles, five events, and three artifacts. The roles are Product Owner, Scrum Master, and Developers; the events are sprint planning, daily scrum, sprint review, retrospective, and the sprint itself; the artifacts are product backlog, sprint backlog, and increment. It was formalized by Ken Schwaber and Jeff Sutherland in the 1990s and codified in the Scrum Guide (first published 2010, most recently updated 2020). It is the dominant agile framework in industry by a wide margin and the most-commonly-misapplied.
The three roles: Product Owner (owns the product backlog and what gets prioritized), Scrum Master (facilitates the process, removes blockers, coaches the team on Scrum practice, NOT a project manager despite frequent role conflation), and Developers (the cross-functional team that builds the increment; the 2020 Scrum Guide renamed them from "Development Team" to make the cross-functional nature explicit). The five events: the sprint (a time-boxed iteration, fixed length, no scope changes mid-sprint), sprint planning (define the goal and pull items from the product backlog into the sprint backlog), daily scrum (15-minute standup, focused on coordination not status reporting), sprint review (show the increment to stakeholders and gather feedback), and sprint retrospective (the team reflects on its own process and decides what to change next sprint). The three artifacts: product backlog (the prioritized list of everything that could be built), sprint backlog (what the team committed to this sprint), and increment (the working product output at end of sprint). The Scrum Guide explicitly states that "Scrum is purposefully incomplete, only defining the parts required to implement Scrum theory," meaning teams are expected to layer practices on top. The most common deviation patterns ("ScrumBut"): keeping ceremonies but ignoring sprint goals, treating standups as status reports for the manager, never running retrospectives, allowing mid-sprint scope changes. Each of these breaks Scrum in a way the team doesn't admit to until it stops working.
Ryan's Take
Most "Scrum" in industry is what the Scrum community calls "Scrum-but," as in "we do Scrum, but our retro is optional, our standups are status meetings, our sprints end whenever the work is done, and the Scrum Master is actually the manager." That isn't Scrum, it's a meeting schedule with a Scrum sticker on it. If you're going to do Scrum, do Scrum. The framework only works because the constraints (fixed sprint length, no mid-sprint changes, real retros) force the team to confront problems rather than ignore them. Strip the constraints out and you have meetings. If the constraints don't fit your work, that's a sign to use Kanban instead, not to use broken Scrum.
What founders get wrong: Adopting Scrum without commitment to the Scrum Master role as a real practice. A part-time Scrum Master who's also the engineering manager, the product owner, and a working developer is not facilitating Scrum; they're checking three boxes badly. Either resource the role properly or pick a framework that doesn't require it.
Related: Agile · Sprint · Product Backlog · Kanban · Product Management
FAQ
What is Scrum?
A specific agile framework structured around time-boxed sprints (1-4 weeks), three roles (Product Owner, Scrum Master, Developers), five events (sprint planning, daily scrum, sprint review, retrospective, the sprint itself), and three artifacts (product backlog, sprint backlog, increment). Formalized by Ken Schwaber and Jeff Sutherland.
What are the roles in Scrum?
Product Owner (owns the backlog and prioritization), Scrum Master (facilitates the process and removes blockers, NOT a project manager), and Developers (the cross-functional team that builds the increment; renamed from "Development Team" in the 2020 Scrum Guide).
What is the difference between Scrum and Agile?
Agile is a values-based philosophy from the 2001 Agile Manifesto; Scrum is one specific framework that implements agile values. Other agile frameworks include Kanban, Extreme Programming, SAFe, and LeSS. A team can be agile without doing Scrum; a team doing Scrum ceremonies can still be non-agile.
Find this article helpful?
This is just a small sample! Register to unlock our in-depth courses, hundreds of video courses, and a library of playbooks and articles to grow your startup fast. Let us Let us show you!
Submission confirms agreement to our Terms of Service and Privacy Policy.