EP-08

Story Points vs Hours Incoherent at Item Level

Estimation Precision

Default severity: medium
EstimationQualityBusiness ValueEffort

What it detects

Description is not yet published for this rule in the PRD catalogue.

Detection formula

No published identification formula is available yet for this rule.

Examples in practice

  • A team shows description is not yet published for this rule in the prd catalogue during analysis.
  • Example signal: Description is not yet published for this rule in the PRD catalogue.

Suggested response

Recalibrate estimation precision—check size classes, drift, and BV vs effort trade-offs.

Coaching playbook

Symptom

Description is not yet published for this rule in the PRD catalogue.

Why it matters

When "Story Points vs Hours Incoherent at Item Level" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.

What you can achieve

Recalibrate estimation precision—check size classes, drift, and BV vs effort trade-offs.

Facilitation questions

  • What system change would stop "Story Points vs Hours Incoherent at Item Level" from firing again?
  • What do the cited issues have in common — same root cause or same workaround?
  • Who owns the two-week experiment and how will we verify on the next import?

Run this rule against your own tracker data with Flow Analyzer.

Product tourSign in
EP-08: Story Points vs Hours Incoherent at Item Level — FlowAnalyzer