AI PM Ready

Estimation

How Agile teams estimate work — story points to T-shirt sizing. Adapted for AI's inherent uncertainty and experimental nature.

Estimation in AI is not about predicting the future. It is about creating shared understanding of effort, complexity, and unknowns before a single line of model code is written.

Not this

  • →Hours to completion
  • →A commitment to a date
  • →A performance metric
  • →Something to optimize

This

  • →Relative complexity vs other stories
  • →Shared team understanding
  • →A planning input
  • →A signal when refined wrong

AI-specific inputs

  • →Data readiness uncertainty
  • →Model performance unknowns
  • →Spike results before estimation
  • →Confidence calibration (40–80%)

The Three Dimensions of a Point

Effort

How much work is required — coding, data engineering, model training, feature engineering, deployment.

Complexity

How difficult is the problem — algorithm choice, interdependencies, edge cases, model interpretability.

Uncertainty

How much is unknown — data availability, model convergence, label quality, production behavior.

Why Fibonacci?

The gaps between Fibonacci numbers grow non-linearly — mirroring how estimation uncertainty scales. The difference between a 1 and 2 is meaningful. The difference between a 20 and 21 is not.

This non-linearity is especially apt for AI work, where complexity often scales exponentially — a 13-point story is not "13 times harder than a 1" but it is genuinely in a different risk category.

The Series

123581321?

Check yourself

Four short questions, about 2 minutes. Pass mark 3 of 4.

Was this page useful?