value delivery Archives - Scrum Master Toolbox Podcast

Nate Amidon: Why Scrum Master Success Means Owning the Entire Idea-to-Deployed Pipeline

“Success for a Scrum Master is maximizing value of the product through the organization. That’s a full stop statement.” – Nate Amidon

Running a company of contract Scrum Masters gives Nate a unique perspective on what success actually looks like. For him, it comes down to one thing: are you increasing the value of the product through the system? Everything else is either a leading or lagging indicator. Practically, this means starting with the most fundamental question: why does your team exist? Nate suggests asking three team members separately what the team does and who they do it for — and checking whether the answers match.

Once you have clarity on purpose, you can work with product and the organization to figure out how to measure whether you’re getting closer. But here’s where Nate pushes boundaries: he believes a Scrum Master’s scope isn’t limited to the Scrum team. If success is measured by value flowing through the system, then you have to take ownership of the entire idea-to-deployed pipeline — product prioritization, cross-team dependencies, QA processes, CI/CD, release schedules. You happen to work as a Scrum Master on a team, but your responsibility extends to anywhere value gets stuck.

In this episode, we refer to Vasco’s OTOG (One Team, One Goal) principle and Nate’s previous episode about the brief-execute-debrief cycle.

Self-reflection Question: If someone asked three different members of your team what the team exists to do and who they do it for, would the answers match — and have you checked recently?

Featured Retrospective Format for the Week: Meme Retro

Nate’s favorite retrospective format might surprise you: the Meme Retro. Give everyone 5-10 minutes to find a meme on the internet that describes the last sprint. Then go around the room, share the meme, and explain why you chose it. It sounds lighthearted — and it is — but that’s exactly the point. As Vasco notes, “laughs per minute” is a great metric for retros, because when people are laughing, they can talk about serious issues without defensiveness. The memes give a different angle on what happened during the sprint, surfacing deeper feelings and patterns that traditional formats might miss. It’s especially useful when teams are getting fatigued from running the same retro format over and over.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!

About Nate Amidon

Nate, founder of Form100 Consulting, and a former Air Force officer and combat pilot turned servant leader in software development. Nate has taken the high-stakes world of military aviation and brought its core leadership principles—clarity, accountability, and execution—into his work with Agile teams.

You can link with Nate Amidon on LinkedIn. Learn more at Form100 Consulting.

BONUS: The Agile Organization as a Learning System

Think Like a Farmer, Not a Factory Manager

“Go slow to go fast. If you want to go somewhere, go together as a team. Take a farmer’s mentality.”

Simon contrasts monoculture industrial thinking with the permaculture approach of Joel Salatin. Industrial approaches optimize for short-term efficiency but create fragile systems. Farmer thinking recognizes that healthy ecosystems require patience, diversity, and nurturing conditions for growth. The nervous system that’s constantly stressed never builds much over time—think of the body, trust the body, let the body be a body.

Value Masters, Not Scrum Masters

“We need value masters, not Scrum Masters. Agile is a useful tool for delivering value, but value itself is primary. Everything else is secondary—Agile included.”

Tom makes his most provocative point: if you asked a top manager whether they’d prefer an agile person or value delivery, the answer is obvious. Agile is one tactic among many for delivering value—not even a necessary one. The shift required is from process mastery to value mastery, from Scrum Masters to people who understand and can deliver on critical stakeholder values.

The DOVE Manifesto

“I wrote a paper called DOVE—Deliver Optimum Values Efficiently. It’s the manifesto focusing on delivering value, delivering value, delivering value.” Continue reading BONUS: The Agile Organization as a Learning System

BONUS: Quality 5.0—Quantifying the “Unmeasurable” With Tom Gilb and Simon Holzapfel

Clarification Before Quantification

“Quantification is not the main idea. The key idea is clarification—so that the executive team understands each other.”

Tom emphasizes that measurement is a means to an end. The real goal is shared understanding. But quantification is a powerful clarification tactic because it forces precision. When someone says they want a “very fast car,” asking “can we define a scale of measure?” immediately surfaces the vagueness. Miles per hour? Acceleration time? Top speed? Each choice defines what you’re actually optimizing for.

The Scale-Meter-Target Framework

“First, define a scale of measure. Second, define the meter—the device for measuring. Third, set numbers: where are we now, what’s the minimum to survive, and what does success look like?” Continue reading BONUS: Quality 5.0—Quantifying the “Unmeasurable” With Tom Gilb and Simon Holzapfel

BONUS: Testing as Measurement—Why Bug-Hunting Misses the Point With Tom Gilb and Simon Holzapfel

The Revelation That Almost Caused a Car Crash

“Tom said like 10 sentences in a row, kind of like a geometric proof, that just so blew my mind I almost drove off the road. I realized I had wasted hundreds of hours in boardrooms arguing about errors of which we were aware of perhaps 10%.”

Simon shares the moment Tom’s framework clicked for him. The insight? Traditional testing—finding bugs and defects—is the wrong focus entirely. It’s a programmer’s view of the world. Managers don’t care about bugs; they care about results, about improvements in their business. Tom calls this shift moving from “testing” to “measurement of enhanced or increased value at every cycle.”

The American Toast Problem

“How do we make toast in America? We burn the toast, and then we pay someone to scrape off the black bits off the bread.”

Vasco invokes Deming’s classic analogy to describe traditional software testing. The entire testing-at-the-end approach is fundamentally wasteful. Instead, Tom advocates for continuous measurement against quantified values. If you expected 3% progress toward your goals this week and didn’t get it, you’ve learned something critical: your strategy needs to change. If you did get it, keep going with confidence.

Four Questions at Every Checkpoint

“Where are we going? Where are we now? Where should we have been at this point? And why is there a gap?” Continue reading BONUS: Testing as Measurement—Why Bug-Hunting Misses the Point With Tom Gilb and Simon Holzapfel

BONUS: Continuous Strategy Engineering—Beyond Waterfall Planning With Tom Gilb and Simon Holzapfel

Strategy Professors Are Decades Behind

“The professors of strategy have no clue as to what Evo is. They are locked in decades ago, waterfall mode.”

Tom’s analysis is stark: the people teaching strategy in business schools haven’t undergone the same agile transformation that software development experienced. They still think in terms of 5-year plans that get tested at the end—a guaranteed recipe for discovering failure too late. The alternative? Decompose any large strategy into weekly value delivery steps. And if you think that’s impossible, ask any AI to do it for you—it will produce 52 reasonable weekly increments in about a minute.

Why OKRs Aren’t Enough for Complex Systems

“If you’re doing small-scale stuff that OKRs were designed for, like planning your personal work 14 days hence, OKRs are wonderful. If you’re designing the air traffic control system for Europe, they’re just too simple.”

Tom distinguishes between tools appropriate for personal productivity and those needed for complex organizational strategy. OKRs force some thinking, which is good, but they weren’t designed for—and have never been adapted to—large-scale systems engineering. His paper “What is Wrong with OKRs?” documents roughly 100 gaps between simple OKRs and what robust value requirements actually require.

Check out Tom Gilb’s paper on what’s wrong with OKR’s and how to fix it.

The Missing Alignment Layer

“We have no mental model for most of leadership about how you actually align people around clear vision.” Continue reading BONUS: Continuous Strategy Engineering—Beyond Waterfall Planning With Tom Gilb and Simon Holzapfel