Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira Reports: Control Chart does not take into account Story Points

Hello,

My team is working in Kanban, and I am using the Control Chart report to view the Cycle Time and analyze team performance.

Stories have different weight (Story Points), however the Control Chart report does not take into account the story points when calculating the average and the rolling average. The calculation is based on the cycle time of the issue itself and the surrounding issues. 

How can story points be reflected in the calculation or by other words how can I get the report based both on story points and cycle time of the issues?  

 

2 answers

2 accepted

Hello @Ludmila Portugeis ,

In fact you shouldn't be analyzing all issues at once on a Control Chart. Keep in mind that most of the time the story point scale is not linear. Even if you are not using a Fibonacci Sequence, it is not healthy to say that a 20 point story is twice as big as a 10 point story. Looking at different issues with different story points would be like comparing apples and oranges. 

Naturally, the Control chart does not have an option to incorporate Story Points into the chart because mathematically it doesn't make sense.

The recommended way would be to look at the Control Chart each time using issues with same (or at least similar) sizes. In that case, you will need to analyze different Control Charts but the results will be meaningful. And (by comparing those charts) you can even discover how story size affects your process.

 

By the way, our team at OBSS built Time in Status app for similar needs. It provides reports that are more detailed and flexible than Control Chart. It is available for Jira Server, Cloud and Data Center.

Time in Status mainly allows you to see how much time each issue spent on each status so you can see status times for each status separately. You can combine statuses in any way into consolidated columns to see metrics like Ticket Age, Cycle Time or Lead Time.

You can also calculate averages and sums of those durations grouped by issue fields you select. For example see the Average Cycle Time for each story point size segment.

tisServer_StatusDuration_Average_CycleTime_perStoryPoint.pngtisServer_StatusDuration_Average_CycleTime_perStoryPoint_Chart.png

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.

Using Time in Status you can:

  • See how much time each issue spent on each status, assignee, user group and also see dates of status transitions. Sort and Filter according to report values.
  • Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
  • Export your data as XLS, XLSX or CSV.
  • Access data via REST API. (for integrations)
  • Visualize data with various chart types.
  • See Time in Status reports on Jira Dashboard gadgets

https://marketplace.atlassian.com/1211756

EmreT

Hi,

I usually create quick filters for groups of stories like 1-3 SP, 5-8 SP, 13 SP or a different grouping and then use the control chart only with these filters active to learn about cycle time.

2 votes
Answer accepted

ups - I wrote this in the wrong section ... so here again:

Hi,

I usually create quick filters for groups of stories like 1-3 SP, 5-8 SP, 13 SP or a different grouping and then use the control chart only with these filters active to learn about cycle time.

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you