What is a Three Amigos meeting — and why it prevents most story failures.
Short answer
A Three Amigos meeting is a short (15–30 min) conversation between a business analyst (or product manager), a developer, and a QA tester that happens before a user story enters the sprint. The three perspectives ensure a story is understood from all angles: what the business wants, what can realistically be built, and what needs to be tested. The output is a shared understanding and acceptance criteria — not a specification document.
The Three Amigos pattern comes from Behavior-Driven Development (BDD) and is widely used in Agile teams independent of BDD tooling. The insight: requirements misunderstood by any one of the three roles — business, development, or QA — lead to the most expensive class of bug: one that's "correct" by spec but wrong by intent.
The three roles.
- Business / Product (the first amigo): understands the goal — what outcome the user story is supposed to produce, who the user is, and why it matters.
- Development (the second amigo): understands the technical constraints — what can be built, what it will require, and where the technical edge cases are.
- QA / Test (the third amigo): understands the failure surface — what could go wrong, what edge cases need testing, and what the acceptance criteria need to cover.
How the session runs.
- Product presents the story: goal, user, and expected behavior.
- Developer asks: "How do you want this to handle [edge case]?" Each question surfaces an assumption that, if left unanswered, would cause a bug or a rework.
- QA asks: "How do we know when this is done?" This produces concrete acceptance criteria: given [context], when [action], then [expected outcome].
- Repeat until no one has another question. Write the acceptance criteria on the story.
The whole thing should take 15–30 minutes per story. Stories that take longer usually need to be split — they're doing too much.
What the session is not. It's not a design session (the solution should already exist at a high level). It's not a scope negotiation (that happened in backlog refinement). It's not a status meeting. Three Amigos is specifically about shared understanding of a defined story before anyone writes code.
The output. Acceptance criteria written in concrete, testable language. Often: a whiteboard or card with Given/When/Then scenarios. Any assumptions surfaced during the conversation, documented and resolved. A story that's ready to enter the sprint without surprises.
When Three Amigos happen at a whiteboard, snap the board with BoardSnap after the session. The AI reads the acceptance criteria, edge cases, and Given/When/Then scenarios and produces a clean story card supplement.
Frequently asked
Do you need exactly three people in a Three Amigos meeting?
Not strictly. The "three" refers to three perspectives (business, development, QA), not three individuals. On small teams, two people may cover all three roles. On larger teams, a fourth person (a UX designer, security reviewer, or data analyst) joins when the story touches their domain. The point is representation of all three perspectives, not headcount.
When should Three Amigos happen in the Agile workflow?
After backlog refinement (the story is sized and prioritized) but before sprint planning (the story enters the sprint). It's part of the Definition of Ready — stories that haven't had a Three Amigos conversation are often not ready to start. Many teams run Three Amigos 1–2 sprints ahead of the story's planned start date.
Is Three Amigos the same as story kickoff?
Similar but not identical. A story kickoff happens when a developer starts work on a story and typically involves the developer asking clarifying questions of the PM. Three Amigos is earlier — it's a pre-sprint quality check that produces acceptance criteria before the story enters the sprint at all. Both practices are valuable; Three Amigos prevents kickoff from being a surprise conversation about missing requirements.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.