TQ-16

Too Few Acceptance Criteria

Text Quality

Default severity: high
ProcessMetrics

What it detects

At most two acceptance criteria lines on AC-required types (Tabuľka 1 #7).

Detection formula

IF issue.type IN ac_required_types AND AC line count ≤ 2 THEN FLAG

Examples in practice

  • Single bullet repeats the summary title.

Suggested response

Cover main, edge, and error paths with at least three verifiable criteria.

Coaching playbook

Symptom

At most two acceptance criteria lines on AC-required types (Tabuľka 1 #7).

Why it matters

When "Too Few Acceptance Criteria" 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

Cover main, edge, and error paths with at least three verifiable criteria.

Facilitation questions

  • What system change would stop "Too Few Acceptance Criteria" 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
TQ-16: Too Few Acceptance Criteria — FlowAnalyzer