Samuel Arendt

A fixed deadline helps choose the scope worth delivering

Most estimate requests arrive with the solution already designed: a list of screens, rules, and integrations for which the team needs to calculate a deadline. The estimate answers how much that will cost. It does not answer whether the problem justifies that cost, and that question is rarely asked before the design.

Shape Up, the method Basecamp published in 2019, calls the answer to that question the appetite. The appetite is a time budget for a standard-size team, set before any solution. As the book puts it, an estimate starts from a design and arrives at a number, while an appetite starts from a number and arrives at a design.

The available time changes the solution

Basecamp works with two sizes of appetite: small projects, one or two weeks for one designer and one or two programmers, and big projects that take the same team six weeks. When a problem does not fit in six weeks, the first attempt is to narrow the problem definition. If that is not enough, the team separates a meaningful part that fits the time.

The size of the appetite changes what counts as a good solution. The book gives simple examples: modeling several database columns or offering a free text field; redesigning the main page to accommodate a feature or placing it on a screen with fewer constraints. Neither option is better in absolute terms. Each is suitable or not for the time the problem deserves.

For whoever decides, this moves the discussion. Instead of negotiating a deadline after the solution already has champions, the conversation about value happens first, when changing course is still cheap.

Narrow the problem before cutting features

A short deadline should not become a list of amputated features. The book shows that the first cut usually happens in the problem definition.

In one of the cases it describes, a customer asked for more complex permission rules, something that could have taken six weeks. Looking into the request, the team found that someone had archived a file without knowing it would disappear for everyone else. A warning on the archive action itself, explaining the effect, solved the problem in one day.

In the other, the request was a calendar view. By asking a customer when she had missed the feature, the team arrived at a smaller and more precise need: seeing free slots to schedule a meeting without having to drive to the office to check the calendar on the wall. The project moved from "do everything a calendar does" to "show free spaces," and it fit the appetite.

In both cases, the time limit forced a question an estimate would not ask: what exactly is going wrong in the work of the person who made the request.

What can be cut and what stays

The chapter on when to stop describes how the team decides scope during execution. Each new item faces direct questions: is it a must-have, could the work ship without it, how likely is this case, and what is the impact if it happens. Whatever is not essential gets marked as optional and is only done if time remains, which in practice almost never happens.

The reference for calling the work done also changes. Instead of comparing with the ideal version, the team compares with how customers solve the problem today. If the result is clearly better than that baseline, it can move on.

Quality is not on that list of cuts. The book uses the experience of finishing its own text: with one week left, the choice was to fix errors instead of adding a new section. A fixed deadline forces the trade-off between time, quality, and scope, and scope is the variable that gives. Without a deadline, the extra section would go in and the errors would stay.

What happens when it does not fit

At Basecamp, the default is not to extend a project that runs over. Extension is an exception and only applies when what remains are must-have items and there are no problems left without a known solution, only execution. Otherwise, the work goes back to be redefined.

Teams that do not use the whole method can still take this rule: agree in advance on what happens if the work does not fit. Without that agreement, the deadline becomes a target that silently stretches, and scope keeps growing.

Where the method has limits

Fixed time with variable scope works when the problem allows more than one good solution. A legal or contractual requirement with scope defined by others does not have that flexibility: there, the minimum scope is given, and what gets negotiated is time, team, or how the work is delivered. In that case, the appetite still helps separate what the obligation requires from what the team would like to include.

Before approving an initiative, whoever decides can write down four answers: how much time the problem justifies, how it is solved today, what is essential in the first version, and what happens if the work does not fit. With that written down, cutting scope stops being an improvisation at the end of the deadline and becomes a decision made at the start.

If your company is weighing something similar, reach me on LinkedIn or WhatsApp.

References

An open cube-shaped frame of metal bars seen from below against a blue sky.

Photo by Josh Sanabria on Unsplash

#Engineering Management, #Software Quality, #Strategy