MI-19
Cross-Tribe Stale Parent Link
Metric Integrity
Default severity: medium
MetricsQualityRisk
What it detects
child tribe differs from parent project tribe after reorg; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- Bulk admin transitions or resolution anomalies distort cycle time and velocity metrics.
- Closure timestamps or fields suggest data repair rather than organic delivery.
- A team shows child tribe differs from parent project tribe after reorg; tests; catalogue during analysis.
Suggested response
Audit closure and field patterns so metrics reflect real completion, not bulk admin updates.
Coaching playbook
Symptom
The "Cross-Tribe Stale Parent Link" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Cross-Tribe Stale Parent Link" 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
Audit closure and field patterns so metrics reflect real completion, not bulk admin updates.
Facilitation questions
- What system change would stop "Cross-Tribe Stale Parent Link" 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.