Skip to main content

Agile Churn

· 2 min read
Roy Russo
Imperator Caesar

Agile Churn: When changes in the list of tasks or scope occur during a Sprint (or iteration).

Churn in sprints is inevitable, but should not be a consistenly occuring event. Stories being added, removed, or story points being adjusted mid-sprint are a fact of life in a dynamic Agile environment, but minimizing disruptions to the team and deliverables should be the goal of every Agile lead.

Finding individial Sprints with high churn and stories that have churned numerous times, can be difficult to reveal within Jira. This is something I've been working on with a few key engineers to extract from the data locked behind JIRA's doors...

Having deployed our new project to a few key friendlies, we have been able to see patterns emerging in their data that point to some correlation with churn...

We all know that churn can be caused lots of context-switching among developers, but our initial discoveries playing with live data from prospects, is that there are other correlaries that deserve some attention:

  1. Too many points in a Sprint
  2. Too many Issues/Stories/Bugs in a Sprint.
  3. Stories with high point values.
  4. Specific Assignees may have higher churn, and lastly...
  5. Specific Creators of Stories may be causing churn with vague acceptance criteria...

The causes for churn are complicated to uncover, and may vary from sprint to sprint, but if churn has become a pattern, it deserves a closer look, as it not only affects deliverable dates, but team morale and future resourcing.