FI-05

Sprint-End Flag Clearing

Flags

Default severity: medium
ProcessOutputRisk

What it detects

Measures how long it takes from when a flag is set to when the first comment or action is taken on the flagged issue. Long processing times indicate the flag mechanism is not being monitored and the escalation path is broken. Computed as a distribution across all flags in the period.

Detection formula

FOR each_flag_event F: flag_date = F.date first_response_date = MIN(comments.filter(created > flag_date, issue=F.issue).created, changelog.filter(date > flag_date, issue=F.issue, field=\'assignee\').date) IF first_response_date IS NULL THEN time_to_response(F) = today - flag_date // still waiting ELSE THEN time_to_response(F) = first_response_date - flag_date Median_response = MEDIAN(time_to_response, all flags in period) IF Median_response > config.fi.max_median_response_days // default: 2 business days THEN FLAG slow_flag_response IF Median_response > config.fi.critical_median_response_days // default: 5 days THEN CRITICAL Report: distribution histogram of response times; per-team breakdown

Examples in practice

  • A team shows measures how long it takes from when a flag is set to when the first comment or action is taken on the flagged issue while max median response days is set to 2 business days.
  • Example signal: Measures how long it takes from when a flag is set to when the first comment or action is taken on the flagged issue.

Suggested response

Close the loop on flags—link blockers, set owners, and clear impediments with traceability.

Coaching playbook

Symptom

Measures how long it takes from when a flag is set to when the first comment or action is taken on the flagged issue. Long processing times indicate the flag mechanism is not being monitored and the escalation path is broken. Computed as a distribution across all flags in the period.

Why it matters

When "Sprint-End Flag Clearing" 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

Close the loop on flags—link blockers, set owners, and clear impediments with traceability.

Facilitation questions

  • What system change would stop "Sprint-End Flag Clearing" 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
FI-05: Sprint-End Flag Clearing — FlowAnalyzer