Contributor Acceleration Index(2.4.10)

Not all team members contribute equally to clearing the backlog — and this visual makes that balance visible. The Contributor Acceleration Index compares how many issues each actor advances (moves to In Progress or Done) against how many issues they create. An index above 1.0 means they are clearing more than they add; below 1.0 means they are adding more than they clear.

This is not a performance ranking — it is a workload balance indicator. A low index may simply mean someone is in a planning or coordination role rather than an execution role. But when a pattern of low-index contributors coincides with backlog growth, it is worth a targeted conversation.

What you can conclude

• Team members with an index well above 1.0 are active backlog reducers — their capacity and focus are aligned with clearing work.
• A team where most contributors are below 1.0 is collectively adding work faster than it is clearing it — a systemic resourcing or scope problem, not individual.
• Use this alongside Sprint Scope Still Open to understand whether unfinished sprint scope is driven by specific contributors or by the team as a whole.

How this chart works

Horizontal bar chart ranking each actor by their Backlog Acceleration Index — the ratio of issues advanced to issues created, pooled across the projects they worked in. Bars are green at an index of 1.0 or above and red below it, and a dashed reference line marks 1.0. An actor who advanced work but created none at all has no finite index (nothing added) and is classified a net reducer. Their bar runs to the end of the axis in a paler fill, labeled "no new items", and is listed first, since no finite index could place it. An index of exactly 0 (issues created, none advanced) is drawn as a short stub so it is not mistaken for a missing bar. Hovering a bar shows the two counts behind it. Accounts Jira reports as apps (such as Automation for Jira) or as service-desk customers are left out of the chart; an account Jira returned no type for stays, labeled unknown, and is never counted as a person.

The date range selects who is listed rather than what is counted: a contributor appears when their most recent activity falls inside the range, and the index shown beside them is computed over their full recorded history, not over the range. That is deliberate — a ratio taken over a few weeks turns on which sprint the window happened to catch. Use the project filter to focus on a specific team.