Using AI in team ceremonies
Practical, safe ways to use AI helpers in agile ceremonies: refinement, sprint planning, stand-ups, reviews and retrospectives, plus meeting notes and reporting. Includes ready-to-use prompts, privacy and trust rules, and where AI should stay out of the room.
๐ฏ By the end of this lesson you will be able to:
- Use AI to prepare for and follow up on refinement, planning, reviews and retrospectives
- Apply privacy, consent and trust rules when using AI with team conversations
- Recognise where AI adds noise or harm, and keep human conversation at the centre
In this lesson
The guiding principle: prepare and follow up, don't replace
Ceremonies exist so people can talk, decide and commit together. AI is most useful before a ceremony (preparing, summarising, spotting gaps) and after it (notes, actions, reports). It should not replace the conversation, make decisions for the team, or monitor individuals.
Backlog refinement
- Draft acceptance criteria and edge cases for a story, for the team to review and correct.
- Spot ambiguous wording, missing information and hidden dependencies before the session.
- Suggest how to split large stories into smaller vertical slices.
- Generate test ideas early, so QA can raise risks during refinement.
A refinement prompt
You are helping an agile team refine a user story before the session. Story: "As a customer, I want to change my delivery address after ordering." Context: orders ship within 24 hours; address changes after dispatch go through the courier. List: (1) questions the team should answer, (2) draft acceptance criteria in Given/When/Then, (3) edge cases, (4) ways to split it into smaller stories. Mark anything you are unsure about as an assumption.
A starting point the team challenges and improves, not a finished answer.
Sprint planning
- Summarise the state of the backlog and carry-over work before planning.
- Draft a sprint goal from the top-priority items for the team to discuss.
- Break agreed stories into a first list of tasks.
- Highlight risks and dependencies from story descriptions.
Daily stand-up
Stand-ups are short and conversational, so AI has a small role. A useful one is a daily summary of the board, blocked items and build status shared before the stand-up, so the meeting focuses on collaboration rather than status reporting.
Sprint review
- Draft release notes and a summary of what was delivered, from completed stories.
- Prepare a stakeholder-friendly explanation of technical changes.
- Summarise stakeholder feedback after the review into themes and candidate backlog items.
Retrospectives
- Group anonymous retro notes into themes, which saves time with large teams.
- Suggest new retrospective formats to keep sessions fresh.
- Track action items across retros and flag recurring themes.
Meeting notes and reporting
- AI transcription and summaries help people who missed the meeting and reduce note-taking.
- Tell everyone when a meeting is transcribed, and follow company policy and local law on recording.
- Check summaries for accuracy before sharing; AI can misattribute who said or decided what.
- Use AI to draft status reports from the board and team updates, then edit for accuracy and tone.
Rules for using AI with team conversations
| Rule | Why |
|---|---|
| Use approved tools only | Meeting content often includes confidential plans, customer data and people topics |
| Get agreement before recording | Consent, trust and, in many places, the law |
| Never monitor individuals | AI-based productivity or sentiment tracking damages trust and may be unlawful |
| Humans decide | AI suggests; the team discusses and commits |
| Check before sharing | Summaries can contain errors and misattributions |
What this means for your role
Developer
Use AI to break stories into tasks and surface technical risks before planning, then bring them to the team as questions.
Tester / QA
Use AI to generate test ideas and edge cases ahead of refinement, so quality risks are discussed early.
Business Analyst / PO
Use AI to draft acceptance criteria and spot gaps before refinement, then refine them with the team and stakeholders.
Tech Lead / Architect
Use AI summaries of dependencies and risks to prepare for planning, and keep estimates with the team.
Project / Delivery Manager
Use AI to draft status reports and stakeholder summaries, and always check them before sending.
Scrum Master / Agile
Introduce AI helpers into ceremonies gradually with team agreement, protect psychological safety, and keep the conversation human.
Try it: prepare one ceremony with AI
- Pick a story for your next refinement and use the refinement prompt with an approved tool.
- Mark which suggestions were useful, which were wrong and which raised good questions.
- Share the result with your team and agree together whether and how to use AI in that ceremony.
Key takeaways
- Use AI to prepare for and follow up on ceremonies; keep the conversation and decisions human.
- AI helps most in refinement (criteria, edge cases, splitting), reviews (notes, summaries) and retro theming.
- Estimates belong to the team; AI should only surface questions.
- Use approved tools, get agreement before recording, never monitor individuals and check summaries before sharing.
Key terms
- Backlog refinement
- Regular work to clarify, split and prepare upcoming backlog items.
- Psychological safety
- A shared belief that the team is safe for honest speaking and taking risks.
- Anchoring
- The tendency to rely too much on the first number or suggestion seen.
Check your understanding
Answer all 5 questions. Score 3 or more to complete the lesson.
1. Where does AI help most with team ceremonies?
2. Why should the team, not AI, estimate stories?
3. Someone suggests recording and transcribing retrospectives. What should happen first?
4. Which is a good AI use in refinement?
5. What should you do before sharing an AI-generated meeting summary?