# Sprint planning: estimate from what the change touches

> Estimates go wrong when nobody looked at the code. A five-minute routine for sizing a change by what it touches: entry points, data, callers, tests and edges.

Source: https://hintvo.com/blog/sprint-planning-estimates-from-the-code | Last updated: November 20, 2026 | Reviewed: 2026-11-20

An estimate is a statement about the code, so the fastest way to a better estimate is to look at the code for five minutes before you say a number. Size a change by what it touches, not by how the request sounds.

## Why estimates by feel go wrong

The request arrives in product words: "add single sign-on". The cost lives in code words: session handling, the user table, the middleware every request passes through. The gap between the two vocabularies is where estimates break.

## Count what the change touches

1. **Entry points.** Which routes, handlers, jobs or screens have to change?
2. **Data.** Which tables or columns? Is there a migration, and what happens to the rows that already exist?
3. **Callers.** Who else calls the thing you are about to change? Search for its usages before you promise anything.
4. **Tests.** Are there tests around it? If not, the first part of the work is writing them.
5. **Edges.** Permissions, error paths, old clients, background jobs that read the same data.

## Turn the count into a size

| What you found | What it usually means |
| --- | --- |
| One entry point, no data change | Small. Say so with confidence. |
| Several callers that must keep working | Medium. Most of the time goes to testing, not writing. |
| A migration with existing rows | Plan the rollout as its own piece of work. |
| No tests around the area | Add the time to write them first. |
| You could not find where it lives | Not ready to estimate. Ask for a short investigation. |

## Say the estimate with its assumptions

A number alone invites an argument. A number with its assumption invites a decision: "Two to three days if we keep the current session table. If sessions have to be migrated, that is a separate ticket." Give a range and say what would move it.

## When to ask for a spike

If five minutes in the code did not give you the entry point and the data it touches, the honest estimate is a time-boxed investigation: half a day to find out, then a real number. Teams accept this more easily than a confident number that doubles later.

> **Where Hintvo fits:** in planning, Hintvo shows what a change touches in your own code, each part with its file and line, while the question is still open. Before the meeting, Prepare me writes a one-page briefing from your code. Prepare me briefings need a pack of hours. See [what it does in real meetings](https://hintvo.com/scenarios).

## Related

- [Hintvo AI in real meetings and interviews: 9 scenarios](https://hintvo.com/scenarios.md): What does Hintvo AI actually do in a real meeting or interview?
- [How to prepare for a technical meeting in five minutes](https://hintvo.com/blog/prepare-for-a-technical-meeting-in-five-minutes.md): How do I prepare for a technical meeting when I only have five minutes?
- [How to answer questions about code you did not write](https://hintvo.com/blog/answer-questions-about-code-you-did-not-write.md): How do I answer a question in a meeting about code I did not write?
