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 collaboration practice that brings together three perspectives to refine a backlog item: product or business intent, development feasibility, and testing and quality thinking. Three Amigos improves outcomes by aligning understanding early, when changes are cheaper and misunderstandings can be corrected before implementation.
Three Amigos is often used in contexts influenced by behavior-driven development, but it is useful even without automation. The key is that the conversation produces shared understanding and testable acceptance, not a long document.
Three Amigos perspectives and responsibilities
Three Amigos is named for the three complementary perspectives that reduce blind spots. Titles vary by organization, but the responsibilities are consistent.
- Product or business perspective - clarifies value, priority, rules, and what success means for users and stakeholders
- Development perspective - explores solution options, constraints, and technical risks that affect delivery
- Testing perspective - focuses on acceptance, edge cases, quality risks, and how behavior will be verified
Three Amigos works when all three perspectives have real voice. If one perspective dominates, the session becomes either a design lecture or a requirement review rather than collaboration.
Running a Three Amigos session effectively
Three Amigos sessions are typically short and focused. The goal is to converge on behavior and acceptance, not to solve every detail.
- Timebox the session - keep the meeting short and focused on producing decisions and acceptance evidence
- Start from intent - restate the outcome and why the item matters, including the user context
- Explore examples - use concrete examples to expose rules, boundaries, and assumptions
- Identify risks - surface technical, data, and quality risks early so the team can de-risk intentionally
- Agree acceptance evidence - write acceptance criteria or scenarios and align on verification approach
- Decide next actions - split work, add discovery tasks, or update ordering based on what was learned
Three Amigos is strongest when it happens before work is started. Late sessions often become defect triage or scope negotiation under pressure.
Three Amigos outputs: scenarios, criteria, and shared examples
Three Amigos produces lightweight artifacts that enable development and validation. These outputs should be just enough to make acceptance testable and to reduce rework.
- Acceptance criteria - clear conditions that define when the story is acceptable and complete
- Examples - concrete cases that illustrate rules and boundaries, reducing interpretive ambiguity
- Given-When-Then scenarios - structured scenarios that describe context, trigger, and expected outcome
- Non-functional constraints - performance, security, compliance, or operational expectations relevant to acceptance
- Open questions - explicitly captured unknowns that require discovery, data, or stakeholder decisions
Three Amigos outputs should align with the definition of done. If the quality bar requires security checks or integration tests, acceptance discussions should incorporate that reality.
Benefits and limitations of Three Amigos
Three Amigos creates value when it reduces costly misunderstandings and improves quality outcomes. It also has limitations if used as a ritual without decisions.
- Shared understanding - reduces different interpretations of the same story across roles
- Earlier risk detection - surfaces rule complexity, data issues, and technical constraints before implementation
- Better test design - enables earlier test planning and more effective automation where appropriate
- Reduced rework - clarifies acceptance and edge cases before code is written
- Dependence on participation - loses value if key decision makers or perspectives are absent
Three Amigos works best as part of a broader refinement system that includes slicing, prioritization, and feedback from delivered increments.
Misuse of Three Amigos and guardrails
Three Amigos is often misused as a meeting that produces no decisions, or as a disguised approval gate. Another misuse is turning it into a long session focused on solution design detail rather than on behavior and acceptance.
- Meeting theater - require concrete outputs such as scenarios, criteria, and explicit next actions
- Approval gate - keep the session collaborative and avoid using it to block work through bureaucracy
- Over-designing - focus on behavior and acceptance, leaving implementation options to the team
- Missing stakeholders - ensure decision makers are available or capture decisions needed before starting work
- Late-stage usage - run Three Amigos early in refinement so learning guides slicing and planning
Three Amigos supports agile delivery when it creates shared understanding of behavior, strengthens acceptance clarity, and reduces downstream quality surprises.
Three Amigos is a collaboration practice where product, development, and testing refine work together to create shared understanding of behavior and acceptance