What you will be able to do
- Write prompts that give a usable first answer, and check every answer against its source.
- Set up one home for each piece of work, with its files and standing instructions, so AI starts from the right material every time.
- Turn interviews and workshop notes into ranked problems, requirements, a business requirements document and user stories in your team's style.
- Turn requirements into screens and a clickable prototype, and test it by watching someone use it before anyone builds it.
- Clean up a backlog, plan releases and answer change requests with facts and options.
- Write test cases from acceptance criteria, release notes for each reader and a weekly status report that drafts itself.
- Catch AI errors before anyone relies on them, and apply the law, the client's policy and your own organisation's rules.
- Decide which ideas should become a saved prompt, a reusable skill, a scheduled task or an agent, and brief your IT team on the best one.
What you will cover
Day 1: from the first request to agreed requirements
| Stage | What your team does |
|---|---|
| Base camp | How generative AI works and why it invents things, a tour of Claude and Microsoft 365 Copilot, and the CARE way to write a prompt: Context, Action, Role or Result, Examples. |
| Initiate | From the client's request to a one page product vision, a stakeholder map and a first risk log, with every line traced to its source file. |
| Discover | One question asked across many files at once, research claims checked against their real sources, and the biggest problems ranked by evidence. |
| Define | Workshop notes turned into a requirements map and a business requirements document, checked in a second chat, then user stories in one house style. The release note and user guide are drafted before anything is built, to find the gaps. |
Day 2: from design to switching off the old system
| Stage | What your team does |
|---|---|
| Checkpoint | Spotting the errors in a note written by AI, challenging a confident AI recommendation, and agreeing your team's AI checklist. When the law, the client's policy and your own policy differ, the strictest rule wins. |
| Design | Screens that follow the client's rules, a clickable prototype, and three changes agreed after watching someone use it. |
| Plan | A messy backlog cleaned up, scored and split into releases, a first sprint plan, and the backlog moved into tools such as Jira or Azure DevOps. |
| Build | A change request answered with its impact and three options, and a weekly status report that runs on a schedule. |
| Test | Test scenarios and cases written from the acceptance criteria, and a script that checks the data, read by a person before anyone trusts the result. |
| Release | Release notes for three different readers from one source, a user guide page and a launch email, ready for approval. |
| Operate and improve | A dashboard built from usage data, the key numbers checked against the source, and new backlog items backed by evidence. |
| Retire | A plan to switch off the old system: what is kept, archived or deleted, and a notice for its users. |
| Finish | The best ideas from both days matched to the right level of automation, a one page brief for IT, an AI community for your organisation and a plan for each person for the next 30 days. |
Who it is for
- Business analysts who run workshops and write requirements.
- Product owners and product managers who look after a backlog.
- Project and delivery managers who run software projects, for clients or inside their own organisation.
- Product leads who want one shared way of using AI across their teams.
No AI experience is needed, and nobody needs to write code.
How it runs
- Private classes. Each class is for one company at a time, quoted per group rather than per seat, with examples from your industry.
- In person or live online. Live online with the trainer in your working hours, wherever your team is, or in person at your premises. Travel for classes in person is quoted separately.
- Length. 2 days (14 hours), live with the trainer.
- One product, start to finish. After a first session on the basics, the course follows the life of one product. Each stage runs the same way: learn the idea in 10 to 15 minutes, practise it with AI on the case, and finish with a real piece of work.
- A realistic, fictional case. Your team works for a fictional client, with the files a real project would have: the client's request, a call transcript, interview and workshop notes, a backlog, data and policies. No real client or company data goes into any AI tool.
- Small groups, with roles. At each stage one person runs the task in Claude, one or two run it in Copilot, and the others check the sources and take notes. Then the group compares the answers. Roles rotate, so everyone tries each one.
- Ideas for your own work. After each stage, everyone writes down one task from their own job that AI could help with. Each group shows its best ideas at the end of each day, and the class votes.
- Language. Delivered in English.
What is included
- 2 days of live, practical training with the trainer
- One course page with every prompt, case file and guide, to use again after the course
- A student guide with the prompt card, your group's AI checklist, a log of automation ideas and a plan for your first 30 days
- Everything your group produces on the case, from the product vision to the plan to switch off the old system
- An Agile Visa Certificate of Completion
Is this the right course?
- Project managers only? AI for Project Managers is a one day course on plans, minutes, status reports and risks.
- Building a product with AI inside it? AI Product Management covers what changes when the product itself uses AI. This course is about using AI to do the work of building any product.
- AI for every office role? AI-Powered Workplace Productivity covers email, meetings, documents and presentations for all staff.
- Reading first? Our free guide AI for the Product Owner covers backlog refinement, discovery and decisions.
Where we deliver
We run this course for teams anywhere in the world: live online in your working hours, or in person at your premises, across the Americas, the UK and Europe, the Middle East, Africa, Asia, Australia and New Zealand. See where we train.
Part of our corporate AI training for teams.
Frequently asked questions
How much does AI for Business Analysts, Product Owners and Project Managers cost?
We run it as a private class for your company and quote per group, not per seat. Tell us the number of people, the format and where they are, and we will send a quotation.
How long is the course?
2 days (14 hours), live with the trainer, in person at your premises or online in your working hours.
Is this a coding course?
No. It is a practical course in everyday product work with AI: requirements, user stories, screens, backlogs, tests, release notes and reports. Nobody needs to write code.
Which AI tools do participants use?
Claude in every exercise, with clear steps to do the same in Microsoft 365 Copilot on a work laptop, so people learn both and compare the answers. We agree the accounts and settings with you before the course.
Do people use real client or company data?
No. Everyone works on a fictional case, so no real client or company data goes into any AI tool. After the course, people reuse the prompts on their own work, with confidential details removed and within your organisation's AI policy.
Who delivers the training?
Founder Prashant Shinde, with 20+ years of training delivery and coaching. Agile Visa, founded 2017, has trained 75,000+ professionals across 140+ countries.
Bring this course to your product team
Tell us the number of people, where they are and when. We reply with an agenda and a quote.
Request a quote Book a discovery call