03 · AI AGENTS FOR OPERATIONS · GENERALI ESPAÑA
AI agents for operations
Turning Jira into a knowledge base the team could actually ask.
- Employer
- Accenture
- Client
- Generali España
- Role
- Designer, builder and driver of adoption
- Period
- Jan – Sep 2026
- Tools
- JiraRovoClaude
AI in production
In short
Problem
Requirements, reviews and test checks took 8–10 hours a week and depended on a few people's knowledge.
What I did
Designed and built four AI agents in Jira with Rovo and drove their adoption.
Result
1–2 hours a week instead, with about half the programme team using the agents.
1–2h
a week on requirements and reviews
down from 8–10 h
4
agents along the requirements-to-UAT chain
requirement, story review, test coverage, UAT status
~50%
of the programme team using them
a ~50-person team
AI agents for operations
Generali España · Accenture client · January – September 2026
The challenge
On the core platform programme, turning a business need into an approved user story was slow and depended on a few people's knowledge. Writing requirements, reviewing user stories and checking test coverage took at least 8–10 hours a week, and onboarding someone new meant explaining everything story by story, because nothing was documented.
My role
I identified the problem, designed and built the agents myself, and drove their adoption across the programme.
The approach
I realised Jira could be more than a tracker: with its AI assistant, Rovo, it could become the programme's knowledge base. I built a set of agents along the chain from requirement to UAT: a requirements agent that turns unstructured input into a structured requirement and creates it directly in Jira, in the right project and with the right fields; a user-story validation agent that compares a story with its requirement, flags what is and isn't covered, reviews the acceptance criteria and suggests missing scenarios; a test-coverage agent that checks whether test cases cover every acceptance criterion; and UAT status reporting from test execution and reported defects. With Rovo as a knowledge layer, anyone could find out what had been decided and where things stood, without depending on whoever held that knowledge.
HOURS A WEEK ON REQUIREMENTS, REVIEWS AND TEST CHECKS
8–10 h1–2 hwith agents
1. Requirement
"Agents should see the renewal discount on the quote."→ REQ-87 · Renewal discount on quote AC1 visible on renewal quote AC2 hidden once expired Created in Jira · Household · Quote & Buy
The team
The programme team of around 50 people across the Household and Motor streams, QA, operations and business.
The outcome
From 8–10 hours a week on requirements, reviews and test checks to 1–2 hours, with the agents adopted across the programme.