In 1995, Ken Schwaber was trying to understand why software projects kept missing their deadlines. He took a stack of popular development methodologies to the process control engineers at DuPont’s Experimental Station in Delaware.
They were amused. Schwaber was treating creative, unpredictable work as if it were a repeatable industrial process. Work like that, they told him, needs a different kind of control: check the results often. Then, adjust based on what you find.
That idea became the foundation of Scrum.
Defined vs. empirical process control
Defined process control is the “plan the work, then work the plan” model behind waterfall delivery. It’s a good fit when the goal and the methods will stay stable.
Say you’re building a two-lane highway bridge across a river. Your understanding of the need, the materials, the soil at each bank. Even the definition of “bridge” won’t change much between the first day and the last. A detailed plan up front pays off.
Empirical process control fits work where you learn as you go. When you’re building a new product, or trying to open up a new market, the vision can change week to week. So can the technical approach and even your sense of what customers value. A detailed plan from month one mostly records what you didn’t know yet.
The empirical approach works in small cycles. You carry out a small piece of the plan, look at the results, and adjust the rest of the plan based on what you learned.
The Scrum Guide rests this on three pillars: transparency, inspection and adaptation. Most people shorten it to “inspect and adapt,” with transparency assumed. Sometimes that assumption is too generous, as we’ll see.
Scrum builds three loops into every sprint
Every Agile framework uses some form of inspect and adapt. Scrum is unusual because it doesn’t leave the loops to good intentions. It puts three of them on the calendar, and each one asks a different question.
| Loop | Question it answers | Event | Primary owner |
|---|---|---|---|
| Sprint | Are we on track to meet the Sprint Goal? | Sprint Planning, Daily Scrum | Developers |
| Product | Are we building the right thing? | Sprint Review | Product Owner |
| Team | How can we work together more effectively? | Sprint Retrospective | Scrum Master |
The sprint loop runs every day. The product and team loops run once per sprint.
1. The sprint loop: adjusting the plan daily
Each sprint begins with Sprint Planning. The Scrum Team agrees on a Sprint Goal, picks the Product Backlog items that will help them reach it and works out how to build those items, usually by breaking them into tasks of a day or less.
Together, these make up the Sprint Backlog: the team’s visible plan for the sprint.
That plan starts changing almost right away. At the Daily Scrum, a 15-minute event held at the same time and place each day, the Developers check their progress toward the Sprint Goal and update the plan. A task turns out to be twice as big as expected. An API the team needed isn’t ready. Someone finds a simpler approach.
The Sprint Goal stays the same while the way to reach it changes. The Developers own this loop, because they manage their own work and the Sprint Backlog belongs to them.
When this loop breaks, the Daily Scrum usually turns into a status report. Developers take turns giving updates to the Scrum Master or a manager, and nobody changes the plan. A quick test: if the Sprint Backlog looks the same after the Daily Scrum as it did before, nothing was adapted.
2. The product loop: adjusting direction every sprint
At the end of the sprint, the Scrum Team and its stakeholders meet for the Sprint Review. They look at what was actually built (working product, not slides about it) and agree on where the product stands.
Then they talk about what should come next. Based on that conversation, the Product Owner may reorder the Product Backlog, add or remove items, or change the product’s direction.
The 2020 Scrum Guide calls the Sprint Review a working session and specifically warns against reducing it to a presentation. The warning is there because so many teams do exactly that.
The Product Owner is mainly responsible for making this loop work. That includes getting the right stakeholders in the room, not just whoever has a free hour on Friday afternoon. If stakeholders stop showing up and the backlog never changes after a Review, the product loop has stalled.
3. The team loop: improving how the team works
The Sprint Retrospective closes the sprint. It comes after the Review and before the next Sprint Planning, and it’s a deliberate break from product work.
The team looks at its interactions, processes, tools and Definition of Done. Then it picks one or two improvements to try. “Try” matters here, because a retrospective change is an experiment, and the team checks the result next sprint like any other.
The Scrum Master is mainly responsible for this loop. Often that means protecting the Retrospective from being cancelled when the team says it’s too busy, which is usually when it’s needed most.
The most common failure is action items that disappear. The team writes improvements on sticky notes and never looks at them again. The 2020 Scrum Guide suggests a simple fix: put the most important improvement into the next Sprint Backlog, where it gets the same visibility as product work.
Transparency holds the loops together
Look at the three failures above and you’ll find the same root cause each time: a lack of transparency.
A Daily Scrum that hides real problems can’t adjust the plan. A Sprint Review without honest feedback can’t redirect the product. A Retrospective where people stay quiet can’t improve anything.
You can’t inspect what you can’t see, and you can’t adapt to an inspection you didn’t really do. That’s why the strongest Scrum teams spend as much effort on openness and trust as they do on the events themselves.
Making the loops work for your teams
Each loop catches a different kind of mistake while it’s still small and cheap to fix. Teams that run all three loops for real tend to improve quickly. Teams that only hold the meetings end up with the calendar invites and none of the learning.
Want to coach these loops well? Explore our Scrum Alliance ScrumMaster track: Certified ScrumMaster (CSM), Advanced Certified ScrumMaster (A-CSM) and Certified Scrum Professional – ScrumMaster (CSP-SM).
Leading the change? Certified Agile Leadership (CAL 1) helps leaders build organizations where inspect and adapt is how the business runs, not only how teams run. You can also ask us about enterprise coaching.


