How do we check the productivity of team members with the help of Jira?

[Sangeetha]

As remote work is in for quite sometime, would like to understand how do we check the team members productivity with the help of JIRA?

[John Funk]

Hi Sangeetha - Welcome to the Atlassian Community!

I am not a big fan of using metrics to determine the productivity of an individual. That can lead to weaponization against the employee, which seems unproductive to hang over their head. 

Rather, you can/should measure productivity by team and how well the team is doing in meeting goals and/or producing shippable items. 

This can be a combination of metrics like Throughput/Velocity, Customer Lead Time, etc. There are some good tools to help with that such as Nave and Actionable Agile.

[Jimmy Branton]

Measuring teams is all well and good, but you still have to measure individual performance.  If you have an individual on a team who isn't pulling their weight, that creates a contentious environment.  If there is no way to objectively quantify an individual's work you will have a tough time improving their productivity.

[Chris Boys]

Hi @Sangeetha, welcome to the community!

As @John Funk  mentions, individual metrics will leave your team open to lots of anti-patterns and funny business.  It takes a super strong company-wide culture of transparency and meritocracy to juggle this balance and apply measures genuinely in the context to fuel growth and evolution, whilst holding back from using them as a lazy performance management tool.

That's why at Umano we've created an agile Team Performance Summary, with measures focussed on team practices that lead to stronger agility outcomes and impact.  Our objective is to support your use of your insights for stronger, insight driven communication and collaboration within your team that focuses on amplifying your customer impact.

We group our measures to provide observability into how teams:

• Design & Build (Lead/Cycle Time for speed, Stability for scope change, Completion Rate for predictability & progress)
• Review (PR Size, Review Speed, Time to Merge for quality and speed of review practices)
• Engage (Communication Balance, Responsiveness, Collaboration to unlock information flow, reduce complexity and maintain momentum)

Performance can be viewed as Snapshot (updated daily), Interval, or across the life time of a team's project, enabling teams to observe their trajectory and what experiments or events are impacting their delivery practices over time.

Regarding Umano's snapshot lens, our customers particularly value the ability to self-compare their current performance relative to their usual (rolling median for the last 6 intervals) performance. We also surface the underlying drivers as context to why a team may be above or below it's usual rate of performance.

Interval Reports can be exported as an email.

We run a 30 day free trial, and will populate your project space with 12months of delivery data as default. Let me know here, or on chat @umano.tech if you have any questions and I'll do my best to see if we can help.

Go well!  Chris

[Yuliia_Borivets__SaaSJet_]

Hi @Sangeetha 

Here are the articles about team productivity you may check out (velocity, sprint burndown and others included)

Jira reports for managers: how to measure teamwork productivity and quality

Story points vs. time spent in Jira: how to estimate remote teams

Hope you find this info helpful.