How can I check the amount of user stories generated/started by a Team Member?

Question

I have performance issues with one of my team members. I would like to see if there is a record and or data I can check where this team member has initiated and completed writing the user stories. Please note we don't record time once a user story is generated. Would it be possible to do that without checking the history of each user story?

Filtering the user story by team member/project doesn't give me the exact picture of how much work this team member has done in each story, as generally team assigns stories to the person.

Overall, I am seeking evidence of performance and therefore how many user stories this team member has started and completed.

rosanna.kelly · Answer

Thank you Walter. I actually managed to do it myself. I totally agree that the first port of call is a face-to-face conversation with this team member. Believe me there have been plenty of occasions but still not performing at the best of his capabilities. So, we just gathered data to only use it as a last resort, and if needed be to make the person more self-aware.

Regards,

Rosie

Walter Buggenhout · Answer

Hi @rosanna.kelly,

It will be important to know how your workflow defines when a person starts work and completes it. If this can be identified as statuses in the workflow, you can perform so-called history searches in Jira to retrieve this information.

e.g. the following search would return all the stories that were started by a user last week, assuming that starting work would correspond with changing the status from To Do to In Analysis

Issuetype = Story AND status CHANGED FROM "To Do" TO "In Analysis" DURING
(startOfWeek(-1), endOfWeek(-1) BY UserX

UserX being the user you want to search for.

In a similar way, you can also find the issues that were completed, as long as you can clearly identify how that action is identified in your process.

Apart from the technical capabilities Jira offers to track performance, first and foremost talk with your team members to find out how they are working, where they are stuggling and how you can support them. It's always better to have a conversation as people to people rather than confronting them with a list of issues they are (not) delivering.

Hope this helps!