DEV Community

Cover image for Forecasting Delivery When Scope Keeps Changing
Filipe Albero Pomar
Filipe Albero Pomar

Posted on Originally published at Medium

Forecasting Delivery When Scope Keeps Changing

"Oliver keeps asking for more features. We uncover new stuff as we code. And the bugs. The bugs! We keep finding more than we can fix."

You know this project. You've been on this project.

The question everyone is avoiding is the one your manager is about to ask: can you deliver by end of quarter?

The instinct is to estimate. How much work is left? How fast are we going? Neither is knowable. You don't know what Oliver will ask for next. You don't know what the codebase will surface tomorrow.

But here's the thing. You don't need to know what's coming. You need to know whether the team can handle it.

The Delivery Band

The trick is to stop trying to predict scope and start measuring capacity.

What you want is a chart - the Delivery Band - that shows two things: what the team can comfortably deliver each week, and what they could manage at full stretch. Plot those forward across the remaining weeks of the project, and you have two lines that tell you exactly how much scope the team can absorb.

Anything below the lower line: you're fine. Anything above the upper line: you're in trouble. Anything in between: watch it.

Building it

Do this with the team. It takes twenty minutes and you can download the template here.

  1. Show them how many tickets - bugs and features combined - they've completed in past weeks.
  2. Ask two questions: how many can we comfortably deliver each week? How many would be a stretch?
  3. Plot both forward as a stacked chart across your remaining timeline.

Delivery bands

Say you have six weeks left. The team calls eight tickets a week as comfortable, fifteen as a stretch. That's 48 at comfort, 90 at stretch, by the end of the project.

Great! Now what?

Reading the chart

You're in week two. Count how many tickets - new bugs, new features, backlog items - are sitting in front of you. Say it's 67.

Look it up on the chart. It falls inside the band - above comfortable, below stretch. That means delivery is possible, but tight. Not safe. Not sunk.

That's a real answer to "will it be done on time?" It's not a guess. It's not a shrug.

You're probably thinking: our throughput is all over the place - some weeks fifteen items, some weeks three. How do you build a baseline from that?

You don't use the average. You use the team's own judgement. They know what a normal week looks like and what an exceptional one looks like. An honest "comfortable" number is more useful than a volatile average that flatters the good weeks.

Week by week

Run this check every week. Count, look up, know where you stand. The conversation shifts from "I think we're on track" to "we have 67 items against a band of 48 to 90 - we're inside, but scope can't keep growing."

That's the conversation your manager actually wants to have. And now you can lead it.


Filipe Albero Pomar is an engineering manager and speaker based in London. He writes about AI adoption, engineering leadership, and software delivery. Find him at alpomar.dev.

TechLeadConf 2026 · GenAI London 2026

Top comments (0)