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; } } }

Does ROVO capable of generating Reports like "Predictability Report"/ "Percentage of Spillovers"etct

raj kumar_0m7urv

Hi Team,

I would like to understand whether ROVO is capable of building automated Reports. As a Scrum Master I would like to see what is the "Predictability of Story Completion" of my scrum teams. So when I give it the instructions as "Consider stories from last 5 Sprints and generate me a Report" can ROVO do? or is there any other way with which we can instruct ROVO for building custom reports?

Thank you

Accepted answers

Nikola Perisic

Hi @raj kumar

In order for Rovo to give the predictability data, it should have the previous example of data that Rovo can follow, and data should be added as knowledge base.

All comments

Nikola Perisic

Hi @raj kumar

In order for Rovo to give the predictability data, it should have the previous example of data that Rovo can follow, and data should be added as knowledge base.

raj kumar_0m7urv

Hi @Nikola Perisic

Ok if I share a spreadsheet with data and a sample graph within the Knowledge base. Can I expect ROVO to use that and build me a graph that resembles my sample graph. And can I have that report refresh like our PIE CHART widget in JIRA for example? Hope I was able to explain my need correctly here.

Nikola Perisic

@raj kumar

To have Rovo to create the real-time refreshable data, that would be a limitation. It should be able to create the graphs by using the example you have given.

raj kumar_0m7urv

Ok thank you @Nikola Perisic

Tomasz Kustrzynski ~Advanced Insights~

Hi @raj kumar_0m7urv , I agree with the point that this depends on historical sprint data, and I'd add why that matter for Rovo in particular.

"Committed" is not easy to determine

Predictability is usually completed / committed, where "committed" is what was in the sprint at its start. Jira does not store that as a field. The Sprint field holds where a work item is now and a list of earlier sprints is went through.

Rebuilding.the starting scope needs each work item's change history and Rovo cannot read it today (ROVO-329). So when you ask for committed vs completed over 5 sprints, it's probably comparing against current or final scope in the sprint. The result will look ok, but may still be off.

Native Jira way to calculate predictability

Velocity report already shows committed and completed per sprint, measured the way the board measure them. Divide completed by committed fore each of the last 5 sprints and you have a predictability figure with no AI involved.

If you do you Rovo for this, check the following

Add the agent’s table yourself rather than trusting its totals.
Ask the same question twice in a fresh chat. If the numbers change, it’s reading a different sample each time.
Check its “completed” count with JQL: sprint = "Sprint 42" AND statusCategory = Done. Expect small differences: the Sprint Report counts what was done in the board’s last column when the sprint closed.

Refreshing the report

As @Nikola Perisic said, Rovo produces a point-in-time answer, not a gadget that updates itself. For a standing view, the Velocity gadget on a dashboard is the closes native option, but it shows committed vs completed, not the ratio.

Full disclosure: I work on Advanced Export. Its datasets hold each work item’s sprint membership over time, along with every sprint’s start and completion dates. That makes committed-at-start vs completed-at-close something you can compute with SQL rather than estimate, and you can schedule the result as a monthly Excel or CSV file. You can do it all from Advanced export Rovo agent without writing any SQL. This particular use case is covered in: Sprint predictability and spillover.