DV-29
Multi-Project Work Split in Description Without Decomposition
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
description mentions delivery projects missing from parent graph; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- Assignee, field, hierarchy, or sprint hygiene rules are violated on active work.
- Issues miss mandatory fields or ownership while still in progress.
- A team shows description mentions delivery projects missing from parent graph; tests; catalogue during analysis.
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
The "Multi-Project Work Split in Description Without Decomposition" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Multi-Project Work Split in Description Without Decomposition" 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
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Facilitation questions
- What system change would stop "Multi-Project Work Split in Description Without Decomposition" 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.