Three Amigos
A refinement conversation works when the perspectives that are going to clash are present. If one is missing, the clash happens anyway, only later and with code already involved. Dinwiddie's starting question was a practical one: what to do if acceptance tests aren't automated. His answer was to bring those three points of view together before building. When the work calls for it, design, operations, security, or regulatory compliance are added.
Three perspectives, not three people
The nuance most often lost is right there in the name: it is three perspectives, not three people. In a small team, one person can contribute two of them; in sensitive work, the testing perspective may need two specialists. The practice also goes by other names: Triad (Ken Pugh) and Power of Three (Lisa Crispin and Janet Gregory).
What it is really for: making different interpretations of the same sentence collide before it costs money, rather than dividing up tasks. If the three perspectives agree on everything, either the story is trivial or someone isn't speaking up.
For a specific story, the 25-minute Example Mapping format fits naturally with the Three Amigos and is usually more effective than a long meeting; when a set of stories needs to be addressed rather than a single one, the right format is a writing workshop.
When conversation isn't enough
The Three Amigos resolve uncertainty of interpretation, not uncertainty of knowledge. Liz Keogh turned Dan North's "deliberate discovery" into a complexity scale, ranging from "we've all done this before" to "nobody has ever done this." On the lower rungs, you talk and build; on the higher ones, more talking doesn't help: you have to buy information with a spike or an experiment. When the group has spent 20 minutes speculating, what's missing isn't more conversation; it's a piece of data that nobody has.
The four common mistakes
Its pitfalls are well documented, and there are four:
- Limiting it literally to three people, forgetting that what matters is the perspectives.
- Expanding it to the whole team, which turns it back into a meeting.
- Turning it into a formal recurring event, which bureaucratizes it.
- Arriving with the scenarios already settled, which is the conversational version of the handoff: the session then serves to validate, not to discover.
Common mistake
Turning it into a ritual of three fixed people. The composition depends on the work; freezing it turns the practice into a committee and leaves out necessary perspectives. And its flip side, arriving with the scenarios already decided: if whoever calls the session brings the answer, the three perspectives stop contributing, and the clash of interpretations (which is the whole point) never happens.
Resources
🏦 Skill User storiesState of the art and development guide · Skill Arena
📄 Historias de usuario v.5.0 [User Stories, in Spanish]Free download · Scrum Manager · Jan 2026
📄 Scrum Master en equipos con IA v.1.0 [Scrum Master in Teams with AI, in Spanish]Free download · Scrum Manager
📄 Cómo se crea una historia de usuario [How a User Story Is Created, in Spanish]Scrum Manager Blog · Jan 2023
References
- Dinwiddie, George. (2009). "The Three Amigos" (blog: iDIA Computing).
- Crispin, Lisa; Gregory, Janet. (2009). Agile Testing. Addison-Wesley.
- Pugh, Ken. (2011). Lean-Agile Acceptance Test-Driven Development. Addison-Wesley.
See also
Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.