Three Amigos | Agile Scrum Master
Three Amigos is a collaboration practice where product or business, development, and testing perspectives refine work together to agree expected behavior. It creates value by preventing misunderstandings, improving acceptance clarity, and enabling early test design and automation without locking in implementation. Key elements: a timeboxed conversation, shared examples and scenarios, explicit acceptance criteria, alignment with the definition of done, and follow-up actions to split, de-risk, or clarify work.
Three Amigos purpose in refinement and quality
Three Amigos is a collaborative refinement practice that brings together product or business intent, development feasibility, and testing or quality thinking around the same backlog item. Its purpose is to improve the quality of decisions early, while the team can still adapt cheaply, reduce ambiguity, and protect flow.
Three Amigos creates value when it turns assumptions into shared understanding, examples, and testable acceptance. It is not mainly about holding a meeting or producing documentation. It is about creating a short feedback loop before implementation so the team can inspect what it thinks it knows, expose uncertainty, and adapt the work before avoidable defects, rework, or delay appear.
Three Amigos perspectives and responsibilities
Three Amigos works by combining complementary perspectives that see different risks and different forms of value. Titles vary, but the point is to bring together the people who can best clarify why the work matters, what is feasible, and how the team will know it is done well enough.
- Product or business perspective - clarifies the desired outcome, user context, business rules, priority, and the evidence that the item is worth doing
- Development perspective - explores implementation options, technical constraints, dependencies, and trade-offs that affect delivery and maintainability
- Testing perspective - challenges assumptions through examples, edge cases, risks, and verification thinking so acceptance becomes clear and observable
The practice is strongest when these perspectives can influence the work rather than simply comment on it. If one perspective dominates, the conversation usually becomes a handoff, status checkpoint, or design lecture instead of a collaborative learning loop.
Running a Three Amigos session effectively
Effective Three Amigos sessions are short, focused, and outcome-oriented. The goal is not to solve every detail up front, but to create enough shared understanding for the team to start well, make good trade-offs, and know what still needs discovery.
- Timebox the session - keep the conversation short enough to maintain focus and force clarity on the most important decisions
- Start from intent - restate the user or business outcome, why it matters now, and what problem the item is meant to solve
- Explore examples - use concrete cases to make rules, boundaries, assumptions, and exceptions visible
- Identify risks - surface technical, operational, data, quality, and dependency risks early so the team can respond deliberately
- Agree acceptance evidence - define how the team will know the outcome has been achieved and which checks will give useful feedback
- Decide next actions - split the work, simplify scope, add discovery, involve more perspectives, or reorder the backlog based on what was learned
Three Amigos is most useful before implementation starts, because that is when learning can still improve slicing, ordering, and solution options. When used late, it often becomes expensive correction work rather than early prevention.
Three Amigos outputs: scenarios, criteria, and shared examples
Three Amigos should produce lightweight outputs that improve delivery and validation. The purpose of these outputs is not compliance. It is to make behavior explicit enough that people can build, test, review, and adapt with less confusion and faster feedback.
- Acceptance criteria - clear conditions that define when the item is acceptable in terms of outcome, behavior, and quality
- Examples - specific cases that reveal how rules work in practice and reduce interpretation gaps
- Given-When-Then scenarios - structured expressions of context, trigger, and expected result that help teams think clearly about behavior
- Non-functional constraints - performance, security, compliance, reliability, or operational expectations that must be considered part of acceptance
- Open questions - visible unknowns that need discovery, data, stakeholder input, or a later decision
These outputs should align with the definition of done and with the team’s actual quality bar. If integration, security, supportability, or observability matter in real use, they should appear in the conversation early rather than emerge as surprises near the end.
When to Hold a Three Amigos Session
- Before development starts - use it while learning can still change the shape, size, or order of the work
- When acceptance is unclear - bring perspectives together when success conditions are vague, incomplete, or interpreted differently
- When complexity or uncertainty is high - use it for items with difficult rules, multiple dependencies, meaningful risk, or unknowns
- When similar work has created rework before - apply it where past defects, misunderstandings, or missed expectations show a need for earlier alignment
Typical Agenda
- Present the work item - explain the intended outcome, the user or business context, and why the item matters now
- Explore scenarios - discuss normal flows, variations, edge cases, and failure modes to test assumptions
- Define acceptance criteria - agree on observable conditions and evidence that will show the item is done well enough
- Identify dependencies - expose technical, business, operational, or data constraints that may affect flow or sequencing
- Document agreements - update the backlog item with the minimum useful detail so the shared understanding can travel with the work
Benefits and limitations of Three Amigos
Three Amigos helps when it improves the quality of decisions before coding starts and strengthens the team’s ability to learn during delivery. Its value comes from reducing costly misunderstanding, not from completing a ritual.
- Shared understanding - reduces conflicting interpretations of value, scope, behavior, and quality expectations
- Earlier risk detection - exposes hidden rules, data issues, technical constraints, and edge cases before they become expensive
- Better test design - supports earlier thinking about useful checks, scenarios, and automation where it adds real feedback
- Reduced rework - clarifies acceptance before implementation, which lowers churn, defect escape, and avoidable back-and-forth
- Cross-functional learning - builds stronger shared judgment across product, engineering, and quality over time
- Dependence on real participation - loses value when the needed perspectives are absent, passive, or unable to change the work based on what emerges
It works best as part of a broader refinement system that includes small slices, clear ordering, feedback from delivered increments, and willingness to adapt when new evidence appears.
Best Practices
- Bring the needed perspectives - include whoever can improve the decision, even when that means more than three people
- Keep the conversation lean - use short timeboxes and stay focused on behavior, risks, and acceptance rather than exhaustive analysis
- Use concrete examples - anchor the discussion in realistic situations so hidden assumptions and boundary conditions become visible
- Connect to ATDD or BDD when useful - turn agreed examples into stronger validation and faster feedback where that helps the team
- Close the learning loop - compare delivered behavior with what was agreed and use that evidence to improve future refinement
Misuses and guardrails
Three Amigos is commonly misused when teams perform the conversation as ceremony instead of using it to improve decisions. It also loses value when it becomes a gate, a long design session, or a late correction mechanism after the work is already underway.
- Meeting theater - this looks like a polite discussion that ends without examples, clarified acceptance, or next actions; it hurts because ambiguity survives into delivery; instead, leave with explicit learning, decisions, and visible follow-up
- Approval gate - this looks like waiting for permission or sign-off before work can move; it hurts because it adds delay and weakens shared ownership; instead, use the session to improve readiness and understanding collaboratively
- Over-designing - this looks like spending too much time on implementation detail before behavior and outcomes are clear; it hurts because it locks in choices too early and reduces adaptability; instead, focus first on intent, examples, constraints, and acceptance
- Missing perspectives - this looks like refining with people who cannot answer key value, feasibility, or verification questions; it hurts because the team gains false confidence; instead, involve the perspectives needed to make the item genuinely clearer
- Late-stage usage - this looks like running Three Amigos after coding has effectively started; it hurts because learning arrives when change is more expensive; instead, use it early enough to influence slicing, sequencing, and risk reduction
- Rigid attendance rules - this looks like insisting on exactly three people even when security, operations, UX, or data expertise is needed; it hurts because important constraints stay hidden; instead, adapt participation to the work
- Skipping small items automatically - this looks like assuming simple work has no ambiguity; it hurts because even small items can hide rules or exceptions; instead, use lightweight Three Amigos conversations whenever clarity is uncertain
- Weak capture of outcomes - this looks like ending the session with verbal alignment only; it hurts because understanding decays and different interpretations reappear later; instead, record the minimum useful acceptance, examples, and open questions
Three Amigos supports agile delivery when it improves shared understanding of behavior, creates earlier and better feedback, and helps the team adapt the work based on evidence before avoidable downstream problems grow.
Three Amigos is a collaboration practice where product, development, and testing refine work together to create shared understanding of behavior and acceptance