Estimation field guide

How Developers Estimate Complexity and Risk

Difficult work is not always uncertain, and uncertain work is not always large. Separating complexity, effort and risk gives developers more precise questions to discuss.

Give each dimension its own question

Complexity

How difficult is the solution? Consider business rules, technical interactions and the reasoning needed to implement and test them.

Effort / scope

How much work is involved? Include implementation, testing, review and documentation. A large amount of familiar work can still be straightforward.

Risk

What remains uncertain? Consider untested assumptions, external dependencies and unknown behavior. Record what would reduce that uncertainty.

These dimensions are a useful conversation structure, not perfectly independent scientific measurements. A dependency can increase uncertainty and add coordination work. Name both effects rather than arguing about which category is the only correct one.

Look for interactions, not lines of code

Complexity often comes from interacting rules. A small change to permission logic can require careful reasoning about roles, exceptions and existing behavior. A larger change that repeats a familiar pattern may be easier to understand. Ask how many conditions must hold together and how the team will demonstrate correctness.

  • Which business rules interact, and where are the exceptions?
  • Does the solution cross architectural boundaries or require unfamiliar techniques?
  • What makes the behavior hard to test or reason about?

Turn uncertainty into a question you can answer

A risk rating should have a reason. “The external API might be unreliable” is a starting point, not a complete analysis. Identify the unknown behavior, its possible impact and what evidence would change the assessment. Separate known implementation work from an investigation whose outcome may change the story.

  • Which assumption have we not verified?
  • Whose decision or delivery does this work depend on?
  • What short investigation would reduce the most consequential uncertainty?

Compare three versions of the export story

Illustrative example — not a customer report

  1. Many familiar fields, established export mechanism: substantial effort can coexist with low complexity and low uncertainty. Count the implementation and test work without calling every large item technically difficult.
  2. Few fields, subtle permission rules: the implementation may be small while the logic is complex. Discuss examples of allowed and forbidden exports before rating.
  3. Simple logic, unknown production volume: the risk concerns performance and reliability. Test the agreed data-volume boundary instead of assuming a higher score solves the unknown.

Calibrate ratings with your team

Select completed stories the team remembers and discuss what low, medium and high mean in each dimension. Use those references when estimating new work. When ratings differ, compare the assumptions first. Consonus shows distributions across the dimensions and maps final ratings using the team’s configuration; it does not turn subjective judgments into certainty.

Record why you chose the final ratings. If a dependency changes or an investigation disproves an assumption, revisit the affected assessment. Do not lower a risk rating merely because everyone has agreed to it.

Ready for clearer estimates?

Bring one story to Consonus. Compare your team’s complexity, effort and risk ratings, discuss the different assumptions and agree on your next step.

Free during public preview. No payment details required.