BH-09
Persevere Epic With Stale Open Children
Backlog Health
Default severity: medium
Product BacklogPrioritizationRiskEffort
What it detects
Persevere (or configured) epic with aged open children; tests; catalogue. POIT-17.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows persevere (or configured) epic with aged open children; tests; catalogue during analysis.
- Example signal: Persevere (or configured) epic with aged open children; tests; catalogue.
Suggested response
Refine or prune ageing, imbalanced, or inconsistently closed backlog items.
Coaching playbook
Symptom
The "Persevere Epic With Stale Open Children" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Persevere Epic With Stale Open Children" 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
Refine or prune ageing, imbalanced, or inconsistently closed backlog items.
Facilitation questions
- What system change would stop "Persevere Epic With Stale Open Children" 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.