nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Improve burndown chart incl sub-task

Elvira_Edenlund

Hi,
I am a Scrum Master & Jira administrator seeing a value in velocity measuring on Sub task level.
I propose to improve the burn down chart to be able to gain more learnings from the sprint.

Add a 'drop down list' in existing 'burn down chart report' covering the scenarios below:
1) Sub-task & Story Point
2) No of Sub tasks
3) Storys & Story Point
4) No of Storys
(5. Storys and T-shirt sizes)

All these gives valuable learnings to bring to the team on both individual level and team level, to get better on estimating time and improve predictability for sprint. This data is important especially in a newly created team with little knowledge in Scrum.

(Background: Hardware business: We are using Story to bring a value, Sub tasks to describe the work needed and each resource are estimating time in story point on sub-task level. We use T-shirt size on Story Level to get early estimates on velocity.

Accepted answers

Nic Brough -Adaptavist-

You've got a bit of a problem here, one which can be summarised as "your process is not Scrum".

Jira Software's scrum boards are built to support scrum, so they are not going to work for your process. The main reason for this is that scrum does not have anything to say about non-sprint items, and sub-tasks in Jira are not sprint items, they are a fragment of their parent issue.

A sprint estimate on a sub-task is an irrelevance, as it is already part of the parent, or at least should be.

If you are doing scrum, you do not put sprint estimates on sub-tasks, and you do not look at them to derive velocity.

There's another problem in your question when you say "individual velocity". That is not what velocity is for, it is for the team.

So, the first thing to do is look at your process - if it works for you, then that's fine, but you're going to need to change it to fit with Scrum, or do some work in the Scrum tool to make it fit (if you want to estimate on sub-tasks, you're going to need to build something that takes account of them on the sprint items, and educate your not-quite-scrum teams on how to use it)

All comments

unknown

Hello @Elvira_Edenlund

If you Google 'jira burndown chart subtasks' you will see how many times that topic has been discussed before. The search results will also lead you to JSWSERVER-6007 which is the existing feature request for adding sub-tasks and their story points to burndown charts.

Feel free to add your vote to the feature request, but now that Jira Server is a discontinued product, it's probably a moot point.

Elvira_Edenlund

Great, I have votes and watching the issue.

I have a propose a usability solution with drop down list on different scenarios to optimize the usage of the burn down chart during the team retrospective. I can't see this is included in the feature, so I hope you can take that on also.

If you could add assignee velocity for a sprint that would be a great feature also i.e use filter in burndown chart.

unknown

Paid add-ons like Advanced Burndown Chart allow you to create custom charts that show story point burndown per sprint per person.

If you wanted the additional capability of being able to lookup story sub-tasks using JQL and using that as a filter for an advanced burndown chart, then I believe JQL Booster pack will add that functionality to JQL. Refer to this prior thread on that topic.

Elvira_Edenlund

Hi,

I understand paid add-ons might see like a good solution for Atlassian, but not manageable for me working at a huge company. This is basic scrum need to be able to monitor velocity on program and team level and if you can´t provide it as basic functionality in JIRA I guess we will start using other scrum IT tool which is in discussion for time being.

But now I at least know that Atlassian will not provide this functionality due to use if paid add-ons strategy Atlassian have. Thanks for that knowledge.

Pease, let me know if I have misinterpreted the situation.

Nic Brough -Adaptavist-

You've got a bit of a problem here, one which can be summarised as "your process is not Scrum".

A sprint estimate on a sub-task is an irrelevance, as it is already part of the parent, or at least should be.

If you are doing scrum, you do not put sprint estimates on sub-tasks, and you do not look at them to derive velocity.

There's another problem in your question when you say "individual velocity". That is not what velocity is for, it is for the team.

Elvira_Edenlund

I can here you have not worked with the transition nor as a scrum master in change or not mature scrum teams.

I rest my case.

Elvira_Edenlund

Recommendation is to start to listen in to scrum masters need instead of trying to educate. Big mistake.

Elvira_Edenlund

For your understanding. I am working in hardware business and scrum and agile work differs a lot from SW business. Learn the difference and you will understand why this is needed in Sub-task level. The challenges in HW development are completely different from SW development!

Elvira_Edenlund

Hi,

I agree that the company I am working for is not fully working according as you in Jira/Atlassian team is thinking we should. The company has 25 000 employees and as scrum master I need to find solutions in this HW environment which is not fully agile or scrum and have its own configuration of Jira not complying with you vision. In this configuration we need burndown of subtasks.

The management has ideas that I do not have the possibility to change and need to comply with. In this challange we need to have sub-tasks for burn down charts. I have insight in at least 3 programs with this need. And the company is looking into IT infrastructure right this moment and are looking to use other IT tools (Planview Leankit).

If you can´t adapt that all companies are different from you idea of scrum and configuration of Jira, I am sorry for you lacking in ability to adapt to customer need. Maybe you can provide scrum jira courses to management teams? Sound easier ;/

This is my last input to this issue. I have understood where Atlassian stands in this matter. You do not need to answer and can close this issue.

Nic Brough -Adaptavist-

I've closed it for you.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

report