FL-02

Sprint-End Bulk Status Transition

Flow

Default severity: critical
ProcessMetricsOutputRisk

What it detects

Proportion of total sprint transitions occurring in the final configured percentage of the sprint duration exceeds the configured threshold.

Detection formula

sprint_tail = config.flow.sprint_end_pct // default: last 20% of sprint duration tail_transitions = COUNT(transitions, date IN sprint_tail) IF tail_transitions / total_sprint_transitions > config.flow.sprint_end_concentration // default: 35% THEN FLAG

Examples in practice

  • 40% of sprint status transitions happen in the last two days of the sprint.
  • Most items jump to Done during the final 20% of the sprint window.
  • The sprint burn pattern suggests end-of-sprint bulk movement rather than steady flow.

Suggested response

Inspect board policy, WIP, and status hygiene so flow matches how work actually progresses.

Coaching playbook

Symptom

Proportion of total sprint transitions occurring in the final configured percentage of the sprint duration exceeds the configured threshold.

Why it matters

When "Sprint-End Bulk Status Transition" 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

Inspect board policy, WIP, and status hygiene so flow matches how work actually progresses.

Facilitation questions

  • What system change would stop "Sprint-End Bulk Status Transition" 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
FL-02: Sprint-End Bulk Status Transition — FlowAnalyzer