How to recognize Story Points achieved by developer in JIRA?

Recognizing Story Points achieved by developer is key to provide transparency to Scrum team in order to reward performers and find out early places that need help. The performers are more likely to assist their team mates when they see that their own efficiency is attributed along with overall team results. The metric will encourage honesty and trust within the team and that’s why it is so important.

There is no standard way to do this in JIRA and that’s why I’ve thought that it might be useful to share. Identification of JIRA issues might happen based on workflow transition events like:

  • the user that transitioned issue from status “In Progress” to “Review”, ‘Testing’, ‘Done’
  • the user that transitioned issue from status “Open” to ‘Review, ‘Testing’ , ‘Done”

and  JQL queries like:

(status CHANGED FROM "In Progress" TO "Review" BY linda.jones) or
(status CHANGED FROM "In Progress" TO "Testing" BY linda.jones) or 
(status CHANGED FROM "In Progress" TO "Done" BY linda.jones)

If your JIRA Admins are open to enhancements (i.e. adding custom fields) there is even better approach that adds more value to your further reporting. It is based on custom fields populated as post function in your workflows as given in our video: Design New JIRA Metrics . These later will be quite handy to use, set objectives and break down metrics by new fields like “Tested by” , “Developed by” aligned with your exact workflow process.

Leave a Reply

Your email address will not be published. Required fields are marked *