Implementing Scrum

Updated

What does implementing Scrum involve?

As of November 2026, implementing Scrum means one Scrum Team (a Product Owner, Developers and a Scrum Master) working in Sprints of one month or less, with the five events, three artifacts and three commitments in the Scrum Guide. The rules are short. The hard part is often the culture around them.

This page is a map from the rules to the real-world fixes. Pick the path that matches your problem.

Four-panel Scrum cartoon by Clark and Vizdos, September 11, 2006. A chicken suggests opening a restaurant called Ham-n-Eggs, and the pig replies, No thanks, I would be committed, but you would only be involved.
The first one, September 11, 2006. © 2006 ImplementingScrum.com. Illustrated by Clark, concept by Vizdos.

Implementing Scrum

Stay Relevant. Learn Real-World Tactics.
Free Cartoons. Every Saturday Morning.

    Once you hit the subscribe button, please check your inbox now / in a few minutes to confirm your subscription so you start receiving your first cartoon this Saturday!

    ​

    You'll also receive a "check-in" email every other Wednesday from Michael Vizdos.

    We respect your privacy. Unsubscribe at any time.

    ​

    Focus. #deliver

    Where are you in your Scrum journey?

    No matter where you are in your agile journey of Implementing Scrum, I want to make sure you get what you need. You may be considering scrum, starting scrum, practicing scrum, coaching scrum, or managing / leading scrum.

    Am I missing something that can help you? Email me what's missing or send me a direct message on LinkedIn.

    Who writes this?

    I'm Michael Vizdos. I became a Certified Scrum Master in January 2004 (CSM #72) and a Certified Scrum Trainer in 2006 (my Scrum Alliance trainer profile).

    Tony Clark drew the cartoons, and we worked out the topics together. I wrote the posts, resources and public pages on implementing Scrum. The first cartoon ran on September 11, 2006, and the weekly email has gone out since. Read the origin of the cartoons.

    What is Scrum, and why does implementing it matter?

    Scrum isn't process theater or a "safe" set of best practices. It's a lightweight, purposefully incomplete framework for teams and organizations that need to deliver real value while problems keep changing.

    What is Scrum built on? Empiricism and lean

    Scrum is built on empiricism (learn by doing, not guessing) and lean thinking (eliminate waste, keep only what adds value).

    What are the three pillars of Scrum?

    The pillars are transparency, inspection and adaptation. Scrum only works if everything is visible, regularly inspected and adapted based on real outcomes.

    If you skip one, you're just playing Scrum.

    What do the Scrum Values have to do with trust?

    The five values are commitment, focus, openness, respect and courage. Trust is the glue: the best Scrum Teams are built on psychological safety and honest conversation.

    Who does what on a Scrum Team?

    A Scrum Team needs three real, explicit accountabilities.

    Product Owner: Owns the backlog, clarifies and prioritizes work, connects every action to the Product Goal, and has the courage (and authority) to say "no." PO Deep Dive

    Developers: Do the work (design, code, test, document), collaborate daily to adapt and plan, and make sure everything meets the "done" quality. Developers Explained

    Scrum Master: Coaches and unblocks, upholds Scrum theory and values, and drives team improvement. Never just a "process cop." Scrum Master Breakdown

    Why so explicit? If anyone wears two hats, accountability suffers. Common Pitfalls (Blog & Cartoon)

    What are the Scrum events?

    Each event exists to maximize learning and delivery. There are no filler meetings.

    The Sprint: The heartbeat. One month or less, with inspection and adaptation all the way to a usable, valuable Increment. Details

    Sprint Planning: The Product Owner clarifies "why," Developers pick what and how, and the Scrum Master keeps it focused and time-boxed. Details

    Daily Scrum: 15 minutes, owned by Developers. It is real, adaptive planning, not a status report. Details

    Sprint Review: A working session with stakeholders. Demo the Increment, adapt the backlog and, most important, learn from the feedback. Details

    Sprint Retrospective: The Scrum Master creates space for honest reflection, and the team agrees on one concrete improvement. Details

    Product Backlog Refinement: Not an official event, but essential. The whole team (not just the PO) clarifies, slices and prepares work for the next Sprint. Cartoon: Product Backlog Refinement in Real Life

    What are the Scrum artifacts and commitments?

    Product Backlog and Product Goal: The evolving, transparent list of everything needed. The Product Owner steers, and Developers clarify, split and estimate. Learn More / Product Goal: The "North Star."

    Sprint Backlog and Sprint Goal: What Developers plan for the Sprint: what to do, how to do it, and why it matters. Learn More / Sprint Goal: The anchor for team focus and adaptation.

    Increment and Definition of Done: The real, valuable work that meets your "done" bar, fully integrated with all previous Increments. Learn More / Definition of Done: The "no-excuses" standard.

    Why do the artifacts matter? The Scrum Values, delivered

    Implementing Scrum? Can I use only part of it?

    You can't cherry-pick. "ScrumBut" leads to pain.

    What does leadership do in Scrum?

    Leaders build environments of trust, clarity and learning. It is about safety and focus, not control.

    Does Scrum still work when AI writes the code?

    The accountabilities stay with the people on the Scrum Team. I have written three posts on what changes and what doesn't.

    What is Focus. #deliver?

    Forget the "hustle." Scrum is about doing less, then finishing and delivering more.

    Get started or go deeper

    FAQ

    How long is a Sprint?

    One month or less. The Scrum Guide says the Sprint is a fixed-length event, and a new Sprint starts right after the previous one ends. Shorter Sprints mean more learning cycles. See The Sprint.

    Who is on a Scrum Team?

    One Scrum Master, one Product Owner and Developers. The Scrum Guide says a Scrum Team is typically 10 or fewer people, with no sub-teams and no hierarchies. See Scrum Master, Product Owner and Developers.

    Can I implement only the parts of Scrum I like?

    You can, but the Scrum Guide says Scrum exists only in its entirety. Leaving out an event, artifact or accountability hides the problems Scrum is built to expose. See Real Scrum works as a system and Avoid snake-oil agile.

    Where do I start if my team is new to Scrum?

    Read the rules first, then name the three accountabilities and run one short Sprint. After that, use the Retrospective to pick one improvement. The Interactive Scrum Guide is the free place to read the rules, and Scrum Journey points you to the right stage.

    Is the Interactive Scrum Guide the official Scrum Guide?

    No. The official Scrum Guide is at scrumguides.org, written by Ken Schwaber and Jeff Sutherland. My Interactive Scrum Guide presents the November 2020 version under Creative Commons Attribution Share-Alike, with my commentary added.

    Is ImplementingScrum.com still online?

    Yes, as this page. implementingscrum.com and www.implementingscrum.com both redirect to michaelvizdos.com/implementing-scrum. The cartoon story is at Origin of the Scrum Chicken and Pig Cartoons.

    Everything you need to Implement Scrum: actually, practically, and in your context. Scrum Cartoons, Scrum podcasts, and straight talk for human teams and AI alike.

    Michael Vizdos

    Written by Michael Vizdos

    Certified Scrum Trainer® since 2006. About me · LinkedIn

    35+ years working with teams around the world on Implementing Scrum. Found this useful? Feel free to share it with your team, or send feedback. I read all of it.

    I sometimes use AI tools to brainstorm, draft and create, including images and video visuals. How I use AI.