Three Amigos
A collaborative practice where a product owner, developer, and tester discuss a user story together to build shared understanding before development begins.
Also known as: Three Amigos Meeting, Specification Workshop, Discovery Workshop
Category: Techniques
Tags: agile, collaboration, requirements, software-development, quality
Explanation
Three Amigos is a practice from agile software development where three key perspectives come together to discuss a user story or requirement before development begins. The "three amigos" represent:
1. **Business (Product Owner/BA)**: Defines what needs to be built and why. Brings the business context, user needs, and acceptance criteria
2. **Development (Developer)**: Determines how to build it. Identifies technical considerations, risks, and implementation options
3. **Testing (Tester/QA)**: Considers how to verify it. Identifies edge cases, failure scenarios, and testability concerns
**How a Three Amigos session works:**
1. The product owner presents the user story and its acceptance criteria
2. The developer asks clarifying questions about scope, constraints, and technical implications
3. The tester challenges assumptions by asking "what if" questions and exploring edge cases
4. The group refines the acceptance criteria together, often discovering gaps, ambiguities, or hidden complexity
5. The session concludes with shared understanding and refined, testable acceptance criteria
**Why three perspectives matter:**
Each role brings a fundamentally different lens:
- **Business** asks: "Is this the right thing to build?"
- **Developer** asks: "Can we build this? What are the trade-offs?"
- **Tester** asks: "How do we know it works? What could go wrong?"
Without all three perspectives, requirements tend to be incomplete. Business alone may overlook technical constraints. Developers alone may miss business context. Testers alone may not understand the intended user experience. Together, they catch issues that no single role would identify.
**When to hold Three Amigos sessions:**
- During backlog refinement, before stories enter a sprint
- When a story seems complex or ambiguous
- Before estimating effort for unfamiliar work
- When acceptance criteria feel incomplete
**Benefits:**
- Reduces rework by catching misunderstandings early
- Produces better acceptance criteria
- Builds empathy between roles
- Distributes knowledge across the team
- Shifts quality left (finding issues before coding starts)
**Tips for effective sessions:**
- Keep sessions short (15-30 minutes per story)
- Focus on one story at a time
- Encourage questions over assertions
- Document refined acceptance criteria during the session
- It's fine to include more than three people, but ensure all three perspectives are represented
The name "Three Amigos" was popularized by George Dinwiddie and is closely associated with Behavior-Driven Development (BDD) and the Specification by Example approach.
Related Concepts
← Back to all concepts