Quote card for An Agile Team Shouldn’t Finish Everything Every Iteration.

An Agile Team Shouldn’t Finish Everything Every Iteration

A common measurement of an agile team is whether team members finish everything they planned in the iteration.

There’s nothing wrong with assessing how adept a team is at finishing what it thinks it can. But no team should be expected to finish everything every time.

That is unrealistic and leads to teams under-committing so they can safely deliver everything.

Excessive Expectations Can Introduce Dysfunctionality

Consider a team I know whose boss (the CEO) told them that if they ever failed to finish everything, he would “take corrective action, up to and possibly including termination.”

That team is not going to pull an aggressive amount of work into their iterations. They’ll try to select enough that they don’t get in trouble for being lazy but not so much that they risk not finishing it all.

An Appropriate Target

I find a good goal for a team is to finish everything they say they will about 80% of the time. That is a good degree of predictability for the business without being impossible for some teams to achieve.

To be really clear, a good agile team should finish 100% of what it plans in 8 out of 10 iterations. I’m not saying a team should finish 80% of its planned work each iteration. That is very different.

Successfully finishing everything every time will be impossible for highly interrupt-driven teams. If a significant portion of your team’s job is to respond quickly to issues, you may want to target a lower percentage.

Don’t Plan It If You Don’t Think You’ll Make It

When trying to finish 100% of its work, 80% of the time, the team should feel like they’ll succeed while understanding, realistically, they won’t every time.

I like to think of it as analogous to a basketball player shooting the ball. A player shouldn’t shoot the ball unless he thinks he’ll score. But, even the greatest player will understand that not every shot is going in the basket.

A great basketball player may make 40–50% of his shots. That’s not enough predictability for most teams, which is why I recommend targeting 80%.

Explore Further

Article artwork for 3 Ways to Help Agile Teams Plan Despite Uncertainty.
Article

3 Ways to Help Agile Teams Plan Despite Uncertainty

Featured

We might not like ambiguity, but it’s a fact of life. Find out how to plan with uncertainty in mind.

Estimating is a pre-requisite to planning. You cannot plan without estimates in mind.
Article

Estimating and Planning Are Necessary for Maximizing Delivered Value

Featured

See why planning and estimating still matter for maximizing value in agile work.

Article artwork for Know Exactly What Velocity Means to Your Scrum Team.
Article

Know Exactly What Velocity Means to Your Scrum Team

Featured

Define velocity clearly so teams use it consistently.

Article artwork for When Planning Should Become A Shared Problem.
Article

When Planning Should Become A Shared Problem

Turn planning pressure into a shared conversation about options and tradeoffs.

Article artwork for Plan Visualizer Tool: Agile Forecasting for Accurate Plans.
Article

Plan Visualizer Tool: Agile Forecasting for Accurate Plans

Show stakeholders how much the team can accomplish, by when, with the MGS Essentials Plan Visualizer.

Text graphic: Estimate first, then decide what to commit to.
Article

Separate Estimating from Committing

Remember the difference between an estimate and a commitment and keep the two activities separate, educating management and customers as necessary.