TI-10
Worklog Entry Sustained Inflation Across Delivery
Time Tracking Integrity
Default severity: medium
EstimationProcessMetricsEffort
What it detects
same worklog id monotonically increased across a longer delivery window; tests; catalogue. Parent epic sustained worklog inflation pattern.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows same worklog id monotonically increased across a longer delivery window; tests; catalogue during analysis.
- Example signal: same worklog id monotonically increased across a longer delivery window; tests; catalogue.
Suggested response
Fix time-tracking states so remaining, spent, and status align with reality.
Coaching playbook
Symptom
The "Worklog Entry Sustained Inflation Across Delivery" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Worklog Entry Sustained Inflation Across Delivery" 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
Fix time-tracking states so remaining, spent, and status align with reality.
Facilitation questions
- What system change would stop "Worklog Entry Sustained Inflation Across Delivery" 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.