Entry/Exit Three Amigos
Tags: threeamigos, team, process, agile
Published: 2019-02-10 08:54:48

---
title: Entry/Exit Three Amigos
published: true
description: Entry/Exit Three Amigos are agile rituals that facilitate a minimum level of shared understanding for the units of work that flow in and out of a team's value stream.
cover_image: https://thepracticaldev.s3.amazonaws.com/i/wjog2uo0iwjbhwk5cizk.jpg
tags: three amigos, team, process, agile
---

**Entry/Exit Three Amigos** are agile rituals that facilitate a minimum level of shared understanding for the units of work that flow in and out of a team's value stream.

The Agile Alliance definition of [Three Amigos](https://www.agilealliance.org/glossary/three-amigos/) explains what and why, but is not prescriptive over the process. The implementation details are left up to the practitioner to fill in.


### Agile Alliance Definition:

> Three amigos refers to the primary perspectives to examine an increment of work before, during, and after development.  Those perspectives are:
- **Business** - What problem are we trying to solve?
- **Development** - How might we build a solution?
- **Testing** - What about this, what could possibly happen?


### Entry/Exit Three Amigos Process

> So, a Product Owner, a Developer, and a Tester walk into a bar, sit down, and begin to talk about something that the system under development should do. The Product Owner describes the user story.  The Developer and Tester ask questions (and make suggestions) until they think they can answer the basic question, “How will I know that this story has been accomplished?” - 

---

Keeping in mind a Lean Startup (Continuous Delivery, DevOps, Product Driven, etc) mindset, the conversation should revolve around a hypothesis, what does **done** look like, and determining ways to extract learning outcomes. They should occur *at least twice, entry and exit, per backlog item* that makes its way through the value stream. Additional ad hoc amigos meetings should occur as the details of the work, or customer, demand necessary pivots.

I would prefer the amigo personas to be named: *Product, Engineer, Quality*. Different nomenclatures that create a slightly different picture. At its best, this would be a two minute meeting between the product owner, a software developer, and quality/automation specialist about the feature outcomes. At the other extreme, it becomes an extended conversation that yields to a refinement meeting. Teams should not work on items in which the scope and vision cannot be agreed upon.

Team members may step in and fill a persona, when the subject matter expert is not available, if he/she has the necessary domain knowledge to put on that 'hat'. *IE an engineer putting on a 'Quality' hat*.


## Suggested Process

A checklist makes a great starting points to adapt a new process. The following checklist are team artifacts that I have used to help initially facilitate these meetings. This is a team skill. Start small with relatively well defined work items!


### Entry Three Amigos Checklist

[ &nbsp; ] - Product backlog item meets team **[definition of ready](https://dev.to/dev3l/definition-of-ready--1jfb)**
[ &nbsp; ] - Each amigo represented: **PO / DEV / QA**
[ &nbsp; ] - Time-boxed at **15 minutes** or less
[ &nbsp; ] - Target outcomes (**hypothesis**) presented
[ &nbsp; ] - **Feature introduced** by subject matter expert
[ &nbsp; ] - Similar system functionality identified
[ &nbsp; ] - Conditions of satisfaction (**[gherkin](https://dev.to/dev3l/behavior-driven-development-bdd-crash-course-170)**) finalized
[ &nbsp; ] - Three amigos **agree upon [definition of done](https://www.scrumalliance.org/community/articles/2008/september/definition-of-done-a-reference)**


### Exit Three Amigos Checklist

[ &nbsp; ] - Product backlog item meets team **[definition of done](https://softwaredev3loper.wordpress.com/2016/03/27/definition-of-done/)**
[ &nbsp; ] - Each amigo represented: **PO / DEV / QA**
[ &nbsp; ] - Time-boxed at **15 minutes** or less
[ &nbsp; ] - **Feature introduced** by DEV
[ &nbsp; ] - DEV demos conditions of satisfaction
[ &nbsp; ] - QA / PO accepts or rejects user story transition

---

#### References

- [If you don’t automate acceptance tests?](http://blog.gdinwiddie.com/2009/06/17/if-you-dont-automate-acceptance-tests/)
- [Three Amigos](https://www.agilealliance.org/glossary/three-amigos/)
- [Three Amigos Meeting – Agree the tests before development starts](http://itsadeliverything.com/three-amigos-meeting-agree-the-tests-before-development-starts)
- [How to introduce Story Kickoffs to your team](https://elabor8.com.au/how-to-introduce-story-kickoffs-to-your-team/)