The Three Amigos is a collaborative approach used in Behavior-Driven Development (BDD) to make sure everyone on a project has a shared understanding of a feature before any code is written.
It brings together three distinct perspectives to bridge the gap between business requirements and technical implementation.
The three unique perspectives
The "Three Amigos" typically represents three roles (though it can be more than three people):Â
It brings together three distinct perspectives to bridge the gap between business requirements and technical implementation.
The three unique perspectives
The "Three Amigos" typically represents three roles (though it can be more than three people):Â
-
The business (Product Owner/Business Analyst):Â
- Focus: What problem are we solving? What is the value?Â
- Role: Defines the "What" and provides the requirements.
-
The developer:Â
- Focus: How will we build this? What are the technical constraints?
- Role: Discusses implementation and technical feasibility.
-
The tester:Â
- Focus: What could go wrong? What about the edge cases?Â
- Role: Ensures the feature is verifiable and "breaks" the logic early.Â
How does it work?
Instead of a long document, the Amigos meet for a short session (often 15–30 minutes) to discuss a specific user story.Â
- Scenario Mapping: They turn requirements into concrete examples.Â
- Gherkin Syntax: These examples are often written in the Given/When/Then format.Â
- The Goal: By the end of the meeting, the team should have a set of clear, unambiguous "Acceptance Criteria" that serve as both the guide for development and the blueprint for automated tests.Â
Key benefitsÂ
- Prevents rework: Issues are caught during the conversation rather than during the testing phase.Â
- Shared understanding: Eliminates the "that's not what I meant" friction between departments.Â
- Living documentation: The output (the scenarios) becomes a readable record of how the system is supposed to behave.Â
- The outcome: The Three Amigos turn a vague idea into a "DoR" (the Definition of Ready), meaning the developers can start coding with total clarity, which significantly reduces the chance of a wrong understanding of the actual requirements.Â
