Weekly Team Throughput by Actor(4.5.5)

This visual ranks actors by their average weekly event count and shows each actor's busiest week beside it. It describes how recorded activity is distributed across the team, not the quality or value of anyone's work: a high count can mean delivery, administration or rework.

Questions this can help answer

• Is most of the recorded activity concentrated in one or two actors, and what would happen to that work if one of them were away?
• Where an actor's busiest week sits far above their average, was work arriving in batches, waiting on something, or is that the role's normal cadence?
• Does the ranking match how the team expects work to be shared?

How this chart works

Ranked horizontal bar chart with two bars per actor: average events per week and the events in the actor's busiest week (the peak). Both come from the actor's weekly totals across all of their projects (summed per week first), so the busiest week is never below the average. The average is taken over the complete weeks in which the actor recorded at least one event; a week with no events is not counted as a zero. An actor active on two Jira sites of one organization is shown once per site. With a project selected, both figures cover that project only. Accounts Jira reports as apps (such as Automation for Jira) or as service-desk customers are left out of the ranking; an account Jira returned no type for stays in it, labeled unknown, and is never counted as a person.

The average and the peak both cover complete weeks only. This chart ranks actors rather than weeks, so the week in progress has no bar of its own and enters neither figure.