DG-05

Closure Stage DoD Incomplete

DoD Gates

Default severity: medium
ProcessOutputQuality

What it detects

Issue is in Done status but the configured Done-stage DoD fields are not all completed.

Detection formula

done_stage = config.dod.done_stage_name IF issue.status IN config.workflow.done_statuses AND score(done_stage) \< config.dod.stages\[done_stage\].threshold // default: 1.0 THEN FLAG

Examples in practice

  • Issues advance workflow stages without meeting the configured Definition of Done score.
  • Stage transitions occur before required DoD evidence is present.
  • A team shows issue is in done status but the configured done-stage dod fields are not all completed while done stage name is set to Configured per workspace.

Suggested response

Hold stage transitions until DoD evidence is complete and visible for auditors.

Coaching playbook

Symptom

Issue is in Done status but the configured Done-stage DoD fields are not all completed.

Why it matters

When "Closure Stage DoD Incomplete" 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

Hold stage transitions until DoD evidence is complete and visible for auditors.

Facilitation questions

  • What system change would stop "Closure Stage DoD Incomplete" 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.

Product tourSign in
DG-05: Closure Stage DoD Incomplete — FlowAnalyzer