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

[raj kumar]

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

[Nikola Perisic · Accepted solution]

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]

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]

Ok thank you @Nikola Perisic 

[Howard Berkman]

Hi all.  I wanted to add a practitioner angle to Nikola's answer (which is spot-on about the refresh limitation) — I'd split this into two jobs, because Rovo is great at one and not built for the other.

For the analysis, Rovo shines. You can ask in plain English and it'll pull and interpret the data on demand, e.g.: "Across my last 5 sprints, compare committed vs. completed story points per sprint, calculate the say/do ratio and spillover %, and tell me the trend and the likely causes." It'll even write the JQL to pull committed-vs-completed if you're not fluent in it — handy for prepping a retro or a stakeholder update.

For the living, auto-refreshing report (your pie-chart widget comparison), that's the wall Nikola mentioned — Rovo generates point-in-time and won't maintain a refreshing gadget. For that you're better off with a native Jira dashboard (Sprint/Velocity gadgets + a saved JQL filter), or a marketplace reports app if you want predictability/spillover as a standing chart.

So the pattern that works for me: Rovo for the on-demand "why," native dashboards for the always-on "what." Happy to share the exact prompt I use for the committed-vs-completed breakdown if it'd help.

[Dr Valeri Colon _Connect Centric_]

One small caveat: committed-vs-completed analysis depends on having the right historical sprint data available; Rovo shouldn’t be treated as the source of truth for deterministic metrics.