A common setup in work-tracking tools: an automation rule sets an epic's t-shirt size from its rolled-up story points. 0–20 points is XS, 21–40 is S, and so on up the scale.

It looks like the high-level estimate has been connected to the detailed work. It hasn't. The two have been made mathematically identical.

Why identical estimates are useless

When the size is calculated from the points, the two numbers can never disagree. That sounds like consistency, but it removes the one check that would tell you something important: has the work outgrown the estimate the plan was built on?

The t-shirt size and the story points answer different questions:

  • The t-shirt size is a judgement made early, usually by different people, with less information. It is what funding, roadmaps and commitments were based on.
  • The story points describe the work as it is currently understood, after refinement.

The interesting signal is the difference between them. When the detail grows past the early estimate, the plan built on that estimate needs revisiting. An automation rule that overwrites the size every time the points change makes that signal impossible to see.

What to do instead

  1. Keep the original size. Record the early estimate and leave it alone once the plan is set. If it must change, change it deliberately, with a note of why.
  2. Track the detail separately. Let story points roll up naturally as stories are written and estimated.
  3. Compare the two on a cadence. Map the t-shirt size to a points range and flag items where the rolled-up detail exceeds it.
  4. Treat the larger number as the forecast. If the detail has outgrown the early size, the detail is closer to what will actually happen. If the detail is still smaller, the work probably isn't fully broken down yet, so the early size still stands.

The general rule

Automate the comparison, not the agreement. Estimates at different levels are valuable precisely because they were made at different times with different information. Forcing them to match throws that value away.

Tags: #JiraAutomation #Estimation #AgileDelivery