<![CDATA[Winning Strategy: AI Track]]>https://www.vibhorchandel.com/s/ai-trackhttps://substackcdn.com/image/fetch/$s_!mjtJ!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4e258c32-d257-4e33-8285-eee4e00bd853_256x256.pngWinning Strategy: AI Trackhttps://www.vibhorchandel.com/s/ai-trackSubstackThu, 14 May 2026 13:37:24 GMT<![CDATA[11 things Atlassian Rovo AI can't do yet]]>https://www.vibhorchandel.com/p/11-things-atlassian-rovo-ai-cant-do-yethttps://www.vibhorchandel.com/p/11-things-atlassian-rovo-ai-cant-do-yetThu, 14 May 2026 12:03:46 GMTIn my last post, we looked at how Scrum Masters are successfully using Rovo’s out-of-the-box agents to handle repetitive admin tasks.

But if you’ve used AI for more than a week in the trenches, you know that the demos always look good, and they are nothing like reality. When AI meets a legacy Jira instance, things break.

Rovo is powerful, but it has distinct boundaries.

In this post, I discuss 11 such boundaries of Atlassian’s Rovo AI and how my teams have navigated around them.

Let’s get started.

Got an urgent question?

Get a quick answer by joining the subscriber chat below.

What kind of posts do you want to see on Winning Strategy?

In order to provide you with maximum value out of this publication, please use the above poll and send me your interest.

Read more

]]>