Three amigos sessions — shared understanding captured before a single line of code is written.
Three amigos sessions on a whiteboard create shared understanding between business, development, and testing. BoardSnap captures that shared understanding in a document that prevents rework.
Why scrum masters love this workflow
The three amigos technique — bringing together a business representative, a developer, and a tester to discuss a story before work begins — is one of the most effective rework prevention practices in Scrum. The shared understanding created in that conversation is the real deliverable. But shared understanding that lives only in three people's heads evaporates as the sprint progresses.
BoardSnap preserves the shared understanding. Snap the three amigos whiteboard and get a structured document: the business intent (why this story matters), the technical approach (how the developer plans to implement it), and the test scenarios (what the tester will verify). Three perspectives, one document, written from the actual conversation.
The exact flow
- Set up three sections on the board
Business Perspective, Technical Approach, Test Scenarios. Three columns or three sections. Having the structure visible ensures all three perspectives are explicitly covered.
- Start with the business perspective
What's the user or business need this story addresses? Write it in the business rep's words. The developer and tester should understand the 'why' before discussing the 'how.'
- Document the technical approach
How will the developer implement it? Sketch the approach on the board — API changes, data model implications, dependencies. Write the key technical decisions.
- Write test scenarios from the discussion
For each scenario — happy path, edge case, error state — write a one-line test scenario on the board. These become the acceptance criteria the tester will verify.
- Snap the completed three amigos board
The shared understanding document is captured. All three perspectives are in one document. The story is ready to start without knowledge gaps.
What you'll get out of it
- All three perspectives captured in one structured document — no follow-up clarification needed
- Business intent preserved alongside the technical approach
- Test scenarios written from the actual three-way discussion — more complete than tester-only scenarios
- Shared understanding documented prevents rework from misunderstood requirements
- Three amigos history per story type — patterns in misunderstandings become visible
Frequently asked
When should the Scrum Master facilitate a three amigos session?
For any story with above-average complexity, unclear acceptance criteria, or cross-team dependencies. The Scrum Master identifies these stories during backlog grooming and schedules three amigos before sprint planning.
Can the three amigos session replace the acceptance criteria writing step in backlog grooming?
Yes, and it usually produces better acceptance criteria because all three perspectives are present. The BoardSnap test scenarios section captures the acceptance criteria from the three-way discussion.
What if the three parties disagree during the session?
Write the disagreement on the board explicitly. Mark it as 'Unresolved — needs PO/Architect decision.' BoardSnap captures unresolved items as action items. Don't start the story with unresolved disagreements.
Scrum Masters: try this on your next three amigos.
Three taps. Action items in your hand before the room clears.