Michael Vizdos

Implementing Scrum

You are [hopefully!] here to learn more about Implementing Scrum in the real world.

I want to deliver for you (smile).

I encourage you to subscribe to my weekly Saturday morning "Scrum Chicken & Pig" cartoons and continue reading more on this page (you can click here to read more about the origin of my cartoons).

Your Journey Begins - Or Continues - Today

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

Welcome.

My name is Michael Vizdos, and I'm here to help you.

Am I missing something that can help you?

Please contact me to let me know or connect with me on LinkedIn and send me a direct message.

I need to learn the rules.

I want to understand the Scrum framework, events, and artifacts.

View The Interactive Scrum Guide

I need to fix the culture.

The Scrum rules aren't working because leadership is misaligned.

Learn About Your "First Team"

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 in a world where problems keep changing.

Scrum's Underlying Power: Empiricism & Lean

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

The Three Pillars Of Scrum: Transparency, Inspection, Adaptation

Scrum only works if everything's visible, always inspected, and constantly adapted based on real outcomes. If you skip one, you're just playing Scrum.

Scrum Values Turn Theory Into Action: Trust is the Glue

Success rides on commitment, focus, openness, respect, courage—and above all, trust. The best Scrum Teams are built on psychological safety and honest conversation.

Scrum Team Accountabilities: No Fakes, No "Roles" Games

You need three real, explicit accountabilities for a Scrum Team to work:

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 ensure everything meets "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)

Scrum Events & Activities: Making Real Progress in Rhythm

Each event in Scrum exists to maximize learning and delivery; no filler meetings.

The Sprint — The heartbeat. One month or less. Everything happens here—inspect and adapt all the way to usable, valuable increments. Details

Sprint Planning — PO clarifies "why," Developers pick what and how, Scrum Master keeps the focus tight and time-boxed. Details

Daily Scrum — 15 minutes, owned by Developers: real, adaptive planning (not a status report). Details

Sprint Review — Working session with stakeholders; demo the increment, adapt the backlog, and most importantly—learn and receive feedback. Details

Sprint Retrospective — Scrum Master crafts space for honest reflection. Team together agrees on one concrete improvement. Details

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

Scrum Artifacts & Commitments: Visibility and Alignment, Not Red Tape

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

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

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

Why These Scrum Artifacts Matter: The Scrum Values - Delivered

Implementing Scrum? Use the Whole System.

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

Leadership in Scrum: It's About Safety and Focus, Not Control

Modern Scrum leaders build environments of trust, clarity, and learning.

Focus. #deliver (Doing Less to Achieve More)

Forget the "hustle." Scrum is about doing less—but finishing and delivering more.

Get Started or Go Deeper

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.