SG-07
Worklog Signal — Team Effort Concentration on Single Issue
Signal Chart
Default severity: medium
ProcessMetricsQualityEffort
What it detects
A disproportionate share of a team\'s total worklog for a sprint or period is concentrated on a single issue — one issue is consuming most of the team\'s logged capacity. This is invisible in velocity metrics but highly visible in the signal chart view. team_total_logged(sprint) = SUM(worklog.time_spent, team=T, sprint=S)
Detection formula
FOR each_issue I IN sprint S: issue_share = SUM(worklog.time_spent, issue=I) / max(1, team_total_logged(S)) IF issue_share > config.sg.concentration_threshold // default: 0.35 (35% of team effort on one issue) THEN FLAG effort_concentration Report: issue, logged_hours, team_total, concentration_pctExamples in practice
- A team shows a disproportionate share of a team\'s total worklog for a sprint or period is concentrated on a single issue while concentration threshold is set to 0.35 (35% of team effort on one issue).
- Example signal: A disproportionate share of a team\'s total worklog for a sprint or period is concentrated on a single issue — one issue is consuming most of the team\'s logged capacity.
Suggested response
Use worklog shape (gaps, bursts, handoffs) to coach sustainable pacing and clarity.
Coaching playbook
Symptom
A disproportionate share of a team\'s total worklog for a sprint or period is concentrated on a single issue — one issue is consuming most of the team\'s logged capacity. This is invisible in velocity metrics but highly visible in the signal chart view. team_total_logged(sprint) = SUM(worklog.time_spent, team=T, sprint=S)
Why it matters
When "Worklog Signal — Team Effort Concentration on Single Issue" 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
Use worklog shape (gaps, bursts, handoffs) to coach sustainable pacing and clarity.
Facilitation questions
- What system change would stop "Worklog Signal — Team Effort Concentration on Single Issue" 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.