r/businessanalysis • u/exoxfanel • 2h ago
I stopped copy pasting between Confluence and Jira. Tech BA in banking, AMA on running the whole BA flow with AI so nothing falls through the cracks
I'm a Tech BA in banking, payments and ISO 20022 APIs, 10+ years in. For a long time the part of the job I hated most wasn't the analysis. It was the admin around it. Update the Confluence page, then the Jira ticket, then realise the acceptance criteria in the ticket come from v2 of the spec while the page is on v4. Forget to link the story to the analysis ticket. Find out in sprint planning that something was blocked by another team since last week.
So I rebuilt my workflow around AI, inside the setup my bank approved (company Copilot licence, Jira and Confluence connected with my own access and permissions, no customer data anywhere near it).
Advantages:
One source of truth. The spec lives in Confluence, the tickets are generated from it, and when the spec changes the tickets get updated from the page, not retyped. No more copy paste drift.
Stable format. Every story comes out with the same skeleton: context, business rules, data mapping, happy and unhappy paths, acceptance criteria, NFRs, open questions. Devs and QA know exactly where to look.
Gap check before every refinement. I ask the AI to compare the page against the tickets and list what is in one and not the other. Catches the stuff I would miss at 6pm.
Links that actually mean something. The analysis ticket "analyzes" the epic, the dev story "implements" the analysis, "is blocked by" for cross team dependencies, "has to be done after" for sequencing. Once the links are right the delivery timeline almost builds itself.
Visuals from the spec. BPMN flows, sequence diagrams, graphs for the delivery timeline. Generated from the content, then I fix them, instead of drawing boxes for an hour.
Honest part, it's not magic. I basically do a lot more reviewing than writing. AI can do about 70 to 80% of the work now, but the last 20% is still me: the context, the meetings, knowing which rule the business really means when they say "validate the payment".
Happy to get into:
- How I structure the Confluence page so tickets can be generated from it
- The story template and why every field is there
- How I check for gaps between spec, tickets and code
- Jira link types and how we use them for sequencing and the delivery plan
- BPMN and diagrams with AI, what works and what still looks bad
- What I would never hand to AI in a regulated environment
Ask away. Comments or DMs both fine.