CH-22
Release Date Revised After Active Development Started
Content & History
Default severity: medium
Product BacklogProcessQuality
What it detects
release/target date changed after first active-status entry; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows release/target date changed after first active-status entry; tests; catalogue during analysis.
- Example signal: release/target date changed after first active-status entry; tests; catalogue.
Suggested response
Protect narrative quality: write items before work starts and avoid late or empty edits.
Coaching playbook
Symptom
The "Release Date Revised After Active Development Started" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Release Date Revised After Active Development Started" 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
Protect narrative quality: write items before work starts and avoid late or empty edits.
Facilitation questions
- What system change would stop "Release Date Revised After Active Development Started" 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.