
← Scrum Master Toolbox Podcast: Agile storytelling from the trenches6 nov · 25 min
BONUS AI as the Third Perspective for Agile Delivery With Rohini Prava
BONUS: AI as the Third Perspective for Agile Delivery AI is already changing how agile delivery managers, Scrum Masters, and software teams handle the day-to-day work of delivery. In this BONUS episode, Rohini Prava shares how her team moved from experimenting with Cursor to using AI for practical work: bug analysis, ticket preparation, test planning, reporting, and reducing painful meetings.
From Java Developer to Agile Delivery Manager "I see a good fit. And one of the scrum masters was going on holiday and I got the opportunity, I tried it, I liked it and I think I did well because I was given the role."
Rohini started her career as a Java developer in India, then moved into people management and delivery-focused work before relocating to the UK. A temporary opportunity to cover for a Scrum Master opened the door to a new direction. That experience eventually led her into the Agile Delivery Manager role, where she now leads a distributed team delivering insurance solutions.
When AI Became Part of the Work "It stopped being a curiosity when I integrated it in my work. And the fun started."
For Rohini, the shift happened when her company gave access to Cursor, a developer-focused AI tool. Instead of treating it as something only developers could use, she tested it against real delivery work. The first meaningful example came before a retrospective-style meeting on a difficult project. By giving AI access to project data from Jira Service Management and Azure DevOps, she generated an eight-page analysis in under an hour. The result was a more factual, constructive conversation instead of a meeting based on memory, frustration, or blame.
AI Across the Delivery Team "It really helps the devs to investigate issues, going through the legacy code, because some of the technology they may not even be familiar with."
Rohini describes AI adoption as early, practical, and team-specific. Her team connected Cursor with Azure DevOps through the Model Context Protocol concept, giving the tool useful context about tickets and code. Developers use it to explore legacy code, brainstorm solutions, and support pair-programming-style thinking. Business analysts use it to draft tickets and acceptance criteria. QA team members use it to strengthen test plans and coverage. Rohini uses it for reporting, meeting preparation, email drafting, and pulling useful data from delivery events.
Measuring Impact Beyond Speed "If you're just simply going with, oh, I've used i