TQ-11

Acceptance Criteria Missing Negative or Error Scenario

Text Quality

Default severity: high
ProcessMetrics

What it detects

Story/Feature AC text has no negative path, error, timeout, or failure scenario cues (Tabuľka 1 #2).

Detection formula

IF issue.type IN ac_required_types AND AC text non-empty AND no negative/error edge cues THEN FLAG

Examples in practice

  • AC only states the user sees a list when data loads; no timeout, permission, or empty-data behavior.

Suggested response

Add at least one observable criterion for when the system cannot complete the happy path.

Coaching playbook

Symptom

Story/Feature AC text has no negative path, error, timeout, or failure scenario cues (Tabuľka 1 #2).

Why it matters

When "Acceptance Criteria Missing Negative or Error Scenario" 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

Add at least one observable criterion for when the system cannot complete the happy path.

Facilitation questions

  • What system change would stop "Acceptance Criteria Missing Negative or Error Scenario" 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-11: Acceptance Criteria Missing Negative or Error Scenario — FlowAnalyzer