How to create automated burn down chart based on capabilities

[Shonda]

What is the best way to produce an automated Burn Down Report that has the following requirements:

Squad Level Effort towards specific Capabilities

Sprint level and Monthly level

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Burn charts are about measuring team velocity, they don't talk about capabilities or "level" (whatever you mean by that is unclear to me)

[Bill Sheboy]

Hi @Shonda -- Welcome to the Atlassian Community!

Yes, and...to Nic's ideas:

What problem are you trying to solve by doing that?  Knowing that may help the community to offer you suggestions.  Thanks!

Kind regards,
Bill

[Shonda]

Squad Level Effort towards specific Capabilities is just a way of saying can we break out the velocity per squad per capability?  I haven't seen a way to do that in Jira but that is what I have been asked to check into.  Sometimes we have more than one squad working on a capability and I think this is a way to track each squad's velocity more closely for future planning.

Sprint level and Monthly level means velocity per sprint plus is there also way create a burndown chart based on a month or based on specific dates that are outside the sprint dates?  For instance July 1 through July 31 but the current sprint is July 11 through July 22.

[Nic Brough -Adaptavist-]

I'm afraid I still don't understand what you mean by "capability".  I

t sounds like you mean "issue" (Jira uses the term "issue" to describe "items that need some attention" which could be called story, issue, bug, defect, or anything else)

Are your "capabilities" Jira issues?

[Shonda]

Yes, they are Jira issues which my team uses on a project roadmap grouping epics and other related Jira issues.  They are just above epic issues.  So it would be nice to measure story points per squad per capability being all the rolled up story points for that capability.

[Nic Brough -Adaptavist-]

Ok, they are at a level at which you would not measure velocity (velocity is for each team to judge what they can get done in a time box - you only measure it for the stories the team is dealing with, it's of no use for cross-team reporting).

If you want to accumulate estimates and work recorded upwards, you'll need a script or automation that can calculate it for your capability whenever an estimate is changed on a story, or when work is logged against one.