Agile Glossary

Three Amigos

What is Three Amigos?

Three amigos refer 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 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 examples, leading to a shared understanding for the team.

It’s also good practice 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.

Also Known As

Story Kick-Off huddles or the Triad

Expected Benefits

  • Builds a shared understanding of 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 in 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.

Origins

2009: George Dinwiddie originally used the term “three amigos” in this sense in a blog post titled If you don’t automate acceptance tests?

Further Reading

Join us today!

Agile Alliance offers many online and in-person events and workshops for our members. If you’re not currently a member, you can join now to take advantage of our many members-only resources and programs. LEARN MORE >

Get the latest Agile news!

  • This field is for validation purposes and should be left unchanged.

By subscribing, you acknowledge the Agile Alliance Privacy Policy, and agree to receive our emails.

Additional Agile Glossary Terms

In software development, an "estimate" is the evaluation of the effort necessary to carry out a given development task; this is most often expressed in terms of duration.
Continuous deployment can be thought of as an extension of continuous integration, aiming at minimizing lead time, the time elapsed between development writing one new line of code and this new code being used by live users, in production.
In the context of software development, build refers to the process that converts files and other assets under the developers' responsibility into a software product in its final or consumable form. The build is automated when these steps are repeatable, require no direct human intervention, and can be performed at any time with no information other than what is stored in the source code control repository.
Agile teams generally prefer to express estimates in units other than the time-honored "man-hours." Possibly the most widespread unit is "story points."
Continuous deployment can be thought of as an extension of continuous integration, aiming at minimizing lead time, the time elapsed between development writing one new line of code and this new code being used by live users, in production.
A timebox is a previously agreed period of time during which a person or a team works steadily towards completion of some goal.
Mock Objects (commonly used in the context of crafting automated unit tests) consist of instantiating a test-specific version of a software component.

Help us keep the definitions updated

Ready to join Agile Alliance?

Unlock members-only access to online learning sessions, Agile resources, annual conference discounts, and more! And when you join, you’ll be supporting our member initiatives, regional events, and global community groups.

Privacy Preference Center

IMPORTANT: We have transitioned to a new membership platform. If you have not already done so, you will need to SET UP AN ACCOUNT on the new platform to establish your user profile. Your previous login credentials will not work until you do this set up.

When you see the login screen, choose “Set up Account” and follow the prompts to create your new account. You can choose to log in using your social credentials for either Google or Linkedin (recommended), or you can set up your account using an email address.