TQ-24

Duplicate Requirement Summary in Initiative Scope

Text Quality

Default severity: high
ProcessMetrics

What it detects

Two or more AC-required items in initiative scope share the same summary (~1.6% duplicate titles).

Detection formula

IF normalized summary fingerprint matches ≥2 issue keys in scope THEN FLAG all

Examples in practice

  • Two Stories titled "Improve login performance" with different keys.

Suggested response

Merge duplicates, link as related, or differentiate summaries before creating new work.

Coaching playbook

Symptom

Two or more AC-required items in initiative scope share the same summary (~1.6% duplicate titles).

Why it matters

When "Duplicate Requirement Summary in Initiative Scope" 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

Merge duplicates, link as related, or differentiate summaries before creating new work.

Facilitation questions

  • What system change would stop "Duplicate Requirement Summary in Initiative Scope" 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-24: Duplicate Requirement Summary in Initiative Scope — FlowAnalyzer