CT-07
Lead Time Max Breach: explicit per-issue lead threshold check.
Cycle Time
Default severity: medium
ProcessMetricsOutputRisk
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
- Completion times drift away from the team baseline across recent windows.
- Cycle time metrics show sustained deterioration rather than normal variation.
- A team shows description is not yet published for this rule in the prd catalogue during analysis.
Suggested response
Review cycle-time drivers on the cited work items; tighten WIP or handoffs where delays repeat.
Coaching playbook
Symptom
Description is not yet published for this rule in the PRD catalogue.
Why it matters
When "Lead Time Max Breach: explicit per-issue lead threshold check." 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
Review cycle-time drivers on the cited work items; tighten WIP or handoffs where delays repeat.
Facilitation questions
- What system change would stop "Lead Time Max Breach: explicit per-issue lead threshold check." 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.