DC-01
Code stalled vs pre-release tracker
Delivery Correlation
Default severity: medium
ProcessMetrics
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
- A team shows description is not yet published for this rule in the prd catalogue during analysis.
- Example signal: Description is not yet published for this rule in the PRD catalogue.
Suggested response
Review the observation details with the team and agree one concrete next step to reduce recurrence.
Coaching playbook
Symptom
Description is not yet published for this rule in the PRD catalogue.
Why it matters
When "Code stalled vs pre-release tracker" 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 the observation details with the team and agree one concrete next step to reduce recurrence.
Facilitation questions
- What system change would stop "Code stalled vs pre-release tracker" 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.