Hi Jira Community,
We are currently using Jira for a software project, and our project is set up as a team-managed project. We already have the story points field set up in our issues, and we have two employees. We want to implement a KPI system to reward them based on their story points, sprint completion, and bonus KPIs for extra work done.
Could you advise on the most efficient way to track and monitor story points and sprint completion percentages, especially when the issues vary in complexity? Additionally, how can we handle bonus points for tasks that exceed the initial scope of a sprint? We are looking for best practices or Jira features that can help us automate and streamline this process for maximum efficiency. Thank you!
Hi @Youssef fawzi ,
If you use agile frameworks, I wouldn't recommend incentivizing people individually, but rather as a group.
If you still would like to keep it the way you described, you can use the app I impemented - Multi-team Scrum Metrics & Retrospective.
Using custom JQL filters, you can setup individual metrics, track and retro (embedded in-place mechanism for that) them.
Best regards,
Alexey
Hi @Youssef fawzi -- Welcome to the Atlassian Community!
What behaviors does your company want to foster in people, and why those behaviors?
I recommend starting with those things, communicating them to people, provide timely feedback to progress toward the behaviors, and collaborating to adjust as conditions at the company change. These may help decide which delivery practices the company uses.
Otherwise, you note using Sprints and Story Points, so perhaps this group of people is trying to use the Scrum Framework to manage work. And you describe incentivizing individual contributions using the relative-sizing tool of Story Points. This approach will likely lead to unintended consequences, such as people doing the following:
I recommend learning other approaches to improve agile team and individual leadership for reward systems, such as from your team scrum master / agile coach and sources like Agile Leadership Toolkit: Learning to Thrive with Self-managing Teams, by Peter Koning.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You don't do those things in a team managed project, normally.
Story points are a pretty inexact metric, they are an estimate of (guessed at) complexity, and have nothing to do with time or 'points' in the sense you're trying to use them. If you want to define them as something other than complexity, you might as well use something else like hours, tshirt size, issue count, etc.
Team managed projects are quite simplistic, and they don't really help you set up complicated processes -- though it's not impossible to set it up, you're going to have to learn a lot more about jira, JQL, and how metrics are calculated (then probably jira automation to do the math for you)
The reporting module inside the team managed project is what you get "free:, unless you build more mechanism (Dashboards) and JQL queries to calculate this stuff, or install an add-on that can simplify that for you.
There are some useful reports, but you need to know what Jira expects you to be doing in these projects, and that's a whole other topic. (I'd suggest youtube for how-to videos).
You'll have more luck tracking metrics like story points in a Company managed project, but you'll still need to learn how to use the reporting, and you'll have to follow Sprint practices to get actual accurate metrics, as well as have a correctly set up project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.