{"id":8014826,"date":"2016-06-16T08:53:41","date_gmt":"2016-06-16T15:53:41","guid":{"rendered":"https:\/\/test-agilealliance.pantheonsite.io\/?post_type=aa_glossary&#038;p=8014826"},"modified":"2023-10-18T12:33:30","modified_gmt":"2023-10-18T19:33:30","slug":"three-amigos","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/three-amigos\/","title":{"rendered":"Three Amigos"},"content":{"rendered":"<div>\n<p>Three amigos refer to the primary perspectives to examine an increment of work before, during, and after development. \u00a0Those perspectives are:<\/p>\n<ul>\n<li>Business \u2013 What problem are we trying to solve?<\/li>\n<li>Development \u2013 How might we build a solution to solve that problem?<\/li>\n<li>Testing \u2013 What about this, what could possibly happen?<\/li>\n<\/ul>\n<p>People holding these different perspectives should collaborate to define what to do, and agree on how they know when it is done correctly. \u00a0The 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.<\/p>\n<p>It\u2019s also good practice to review increments of the product that have been implemented to make sure it\u2019s correct from those different perspectives.<\/p>\n<p>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.<\/p>\n<\/div>\n<h2>Also Known As<\/h2>\n<div>\n<div>\n<p>Story Kick-Off huddles or the Triad<\/p>\n<\/div>\n<\/div>\n<h2>Expected Benefits<\/h2>\n<div>\n<div>\n<ul>\n<li>Builds a shared understanding of the intent of an increment of work.<\/li>\n<li>Identifies misunderstandings and confusion early and allows learning to happen sooner in the delivery of an increment of work.<\/li>\n<li>Provides a reasonable guard rail for the number of people who should be involved in discussions about any given increment of work.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<h2>Common Pitfalls<\/h2>\n<div>\n<div>\n<ul>\n<li>Limiting three amigo discussions to only three people. \u00a0If there are other stakeholders who are relevant to a particular increment of work, include them in the discussion.<\/li>\n<li>Expanding the three amigos discussion to the team. \u00a0The intent of this practice is to include each necessary perspective in as small a group as possible.<\/li>\n<li>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.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<h2>Origins<\/h2>\n<div>\n<div>\n<p>2009: George Dinwiddie originally used the term \u201cthree amigos\u201d in this sense in a blog post titled\u00a0<a href=\"http:\/\/blog.gdinwiddie.com\/2009\/06\/17\/if-you-dont-automate-acceptance-tests\/\" target=\"_blank\" rel=\"noopener noreferrer\">If you don\u2019t automate acceptance tests?<\/a><\/p>\n<\/div>\n<\/div>\n<h2>Further Reading<\/h2>\n<div>\n<div>\n<p><a href=\"https:\/\/www.stickyminds.com\/better-software-magazine\/three-amigos\">The Three Amigos: All for One and One for All\u00a0<\/a>by George Dinwiddie<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Three amigos refers to the primary perspectives to examine an increment of work before, during, and after development.  Those perspectives are:<\/p>\n<p>Business &#8211; What problem are we trying to solve?<br \/>\nDevelopment &#8211; How might we build a solution to solve that problem?<br \/>\nTesting &#8211; What about this, what could possibly happen?<\/p>\n","protected":false},"author":12,"featured_media":8067461,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[908],"tags":[674],"class_list":["post-8014826","aa_glossary","type-aa_glossary","status-publish","has-post-thumbnail","hentry","category-process","tag-three-amigos"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/8014826","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/aa_glossary"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8014826"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/8014826\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8067461"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=8014826"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8014826"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8014826"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}