Predictability Gadget In Jira

[Mister Femi]

Hello all, how can I create a JQL filter and gadget to visualize teams' predictability( percentage of committed story points delivered per sprint)? The Jira sprint report bar chart only shows completed vs committed stories, which is not what I am after.

Thank you for your help.

Valentine

[Danut M _StonikByte_]

Hi @Mister Femi

Try our Great Gadgets app.

One of the many gadgets that it offers, is a Team Velocity gadget, which, besides Committed or Completed, can be configured to display percentages like '% Completed' or '% Scope Change'.

Here is an example:

Danut.

[Meghan LaClair]

Hey @Mister Femi  -

If you are open to third party solutions, we provide full insight into this at minware.

Our Sprint Insights dashboard provides a summary panel that helps you visualize historical performance.

We also provide additional insights that allow you to dive deeper into what’s causing predictability issues.

Whether your team(s) is held up paying interest on technical debt, suffering at the hand of scope creep, subject to constant context switching due to poor dependency planning, or simply overbooked in a poor meeting culture, we can help you isolate the anti-patterns so you can work on improving efficiency and team morale.

In addition to sprint insights, we also provide a predictive roadmap that plans around dependencies, weighs weekends, and can be evaluated using task assigning so that you can disperse work in a way that makes the best use of your teams workflow. 

If you would like to check it out we offer a free trial. You can find us in the Atlassian marketplace, or if you would prefer a demo let me know.

Disclaimer: Marketplace Partner

[Bill Sheboy]

Hi @Mister Femi 

There is nothing built-in for Jira which can do ask you ask.  And, IMHO, what you are asking about is not necessarily an indicator of predictability for a team.  (e.g., What does the team think about this as such a predictor?)

That being noted...

The built-in reporting tools for Jira to measure flow are quite limited, and (again IMHO) only help with simple cases and very stable workflows.  When you want to measure to solve a specific problem, I suggest:

• Identify the problem you are trying to solve, what better would look like, how you would know things are better, how you would measure progress toward better, make an experiment to improve, and inspect/adapt as you experiment.
• To measure in support of the experiments...
  • Investigate if any of the built-in reports might help,
  • Investigate marketplace addons for what you want to report/visualize, or
  • Build your own reporting, using custom fields/automation rules, the REST API, or by exporting issues to report in a tool such as a spreadsheet.

Kind regards,
Bill

[Fabio Racobaldo _Herzum_]

Hi @Mister Femi ,

for my knowledge, sprint report will allow you to have information about team velocity and this is the information about the number of story points that team is able to do in each sprint.

After some sprints, team velocity should predict you the correct value for the future sprints 

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/

Hope this clarifies,

Fabio

[Mister Femi]

Thanks @Fabio Racobaldo _Herzum_ You are not wrong. However, what I am after is an SQL filter, gadget that shows the rolling predictability of the team in percentage over 3-6 sprints, calculated in % and represented in a bar chart. Hope that clarifies. 
regards

V

[Fabio Racobaldo _Herzum_]

hey @Mister Femi ,

there is no specific gadget for this. You could try to create your own report through https://marketplace.atlassian.com/apps/1211051/eazybi-reports-and-charts-for-jira?tab=overview&hosting=cloud

Fabio