TQ-15

Acceptance Criteria Prescribe Technical Solution

Text Quality

Default severity: high
ProcessMetrics

What it detects

AC prescribes technical building blocks (API, component, database) instead of required behavior (Tabuľka 1 #6).

Detection formula

IF AC contains solution stack keywords combined with task-style language THEN FLAG

Examples in practice

  • AC names React table component and REST endpoint instead of export behavior.

Suggested response

Describe what must hold; leave implementation choices to the delivery team.

Coaching playbook

Symptom

AC prescribes technical building blocks (API, component, database) instead of required behavior (Tabuľka 1 #6).

Why it matters

When "Acceptance Criteria Prescribe Technical Solution" 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

Describe what must hold; leave implementation choices to the delivery team.

Facilitation questions

  • What system change would stop "Acceptance Criteria Prescribe Technical Solution" 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-15: Acceptance Criteria Prescribe Technical Solution — FlowAnalyzer