Three Amigos
The purpose for the three amigos is higher quality in both the product and the process. This practice seeks to reduce misunderstanding during software development by bringing in the right people to have conversations early.
This small adhoc group is a meeting of the minds of the three primary roles involved in producing software:
Role | Asks |
---|---|
Business | What problem are we trying to solve? |
Development | How might we build a solution to solve that problem? |
Testing | What about this, what could possibly happen? |
People holding these different perspectives should collaborate to define what to do, and agree on how they know when it is done correctly. The end result of such a collaboration results in a clearer description of an increment of work often in the form of Gherkin examples, leading to a shared understanding for the team.
It is also good practice for to review increments of the product that have been implemented to make sure it’s correct from those different perspectives.
The concept of three amigos intends to balance between no collaboration between people with different perspectives and involving an entire team in discussing all the details of every increment of work.
More than a formal meeting, teams should interpret it as an attitude instead of a process, in which the roles continuously collaborate. However teams implement the mindset, it is critical that the three amigos touch base before development begins.
Expected Benefits¶
- Builds a shared understanding about the intent of an increment of work.
- Identifies misunderstandings and confusion early and allows learning to happen sooner in the delivery of an increment of work.
- Provides a reasonable guard rail for the number of people who should be involved in discussions about any given increment of work.
Common Pitfalls¶
- Limiting three amigo discussions to only three people. If there are other stakeholders who are relevant to a particular increment of work, include them in the discussion.
- Expanding the three amigos discussion to the team. The intent of this practice is to include each necessary perspective with as small a group as possible.
- Three amigo discussions become regularly scheduled meetings and are treated as another ceremony for the team to do instead of as a handy guide of what perspectives should be included in a discussion about a particular increment of work.
A helpful technique for three amigos collaboration is Example Mapping, which efficiently identifies rules for acceptance criteria, behavior examples, and open questions. Examples can easily be turned into Gherkin scenarios either during or after the meeting.