Agile & Delivery

Agile Is Not About Doing More Work. It’s About Creating Predictability

The real value of Agile isn’t speed. It’s predictability: knowing what a team can deliver, spotting blockers early and building trust.

One of the most common misconceptions about Agile is that the goal is simply to move faster.

More sprints, more velocity, more tickets closed. If the board is moving quickly, Agile must be working.

I see it differently. The real value of Agile is predictability.

The questions predictability answers

When I think about whether a team’s Agile practice is healthy, I ask questions like these:

  • Can we understand what the team can realistically deliver during a sprint?
  • Can we identify blockers early, while there’s still time to do something about them?
  • Can stakeholders understand where something stands without chasing the development team?
  • When we commit to something, do we usually deliver it?

None of those questions are about raw speed. They’re about whether the organization can plan around the team’s work with confidence.

Why predictability matters more than speed

Picture two teams.

The first team commits to a lot every sprint. Some sprints they deliver most of it; other sprints, half of it rolls over. Stakeholders never quite know what will land, so they hedge: they pad deadlines, escalate early and check in constantly.

The second team commits to less, but delivers what it commits to, sprint after sprint. Stakeholders learn they can trust the plan. Marketing can schedule campaigns around releases. Leadership can make roadmap decisions based on realistic timelines.

Which team is more valuable to the organization? In my experience, almost always the second one.

A team that delivers 80% of its commitments consistently is often more valuable than a team that promises 150% and constantly carries unfinished work into the next sprint. The first team builds trust. The second team builds a backlog of disappointment, even if it’s technically doing more work.

Planning for reality, not the ideal week

In my Web Operations teams, sprint planning isn’t just deciding which tickets fit into the next few weeks. I want us thinking about everything that actually affects capacity:

  • Dependencies on other teams, vendors or approvals,
  • Holidays and PTO,
  • Training time, especially during technology changes,
  • QA effort, not just development effort,
  • Releases and the coordination they require,
  • and unexpected production support, which always shows up.

That last one is particularly important in Web Operations. Production issues don’t wait for a convenient sprint. If the plan assumes 100% of capacity is available for new work, the first incident of the sprint breaks the plan.

So we plan for it. Not by guessing exactly which incident will happen, but by leaving realistic room for the run work that we know, historically, will appear.

Predictability creates a healthier team

There’s a human side to this too. Teams that constantly overcommit live in a permanent state of falling behind. Every sprint ends with unfinished work, and every review is a conversation about what didn’t get done. Over time, that wears people down.

Teams that commit realistically get to finish things. They end sprints with a sense of completion. They have room to do work properly instead of rushing. And when something genuinely urgent comes up, there’s slack in the system to absorb it.

Predictability creates a healthier engineering organization, both in how it’s perceived and in how it feels to work in.

Speed still matters

None of this means speed doesn’t matter. Of course it does. But I’ve found that sustainable speed is usually a byproduct of predictability, not the other way around.

When a team plans realistically, identifies blockers early and finishes what it starts, it naturally gets faster over time. Less rework, fewer context switches, fewer emergency reprioritizations. The work flows more smoothly.

Chasing speed directly often produces the opposite: overcommitment, rushed work, more defects and more time spent recovering.

So when someone asks me how to make a team “more Agile,” I usually start by asking a different question: how predictable is the team today? That’s where the real improvement begins.

Nita Yang Lee

Senior Software Engineering Manager in Atlanta, leading web operations, platform modernization and engineering teams. More about me · Get in touch

Keep reading