During an Agile Testing workshop I learned about the Three Amigos concept and Example Mapping, two interesting ideas for creating better acceptance criteria for user stories. I'll talk about the Three Amigos now and about Example Mapping later on.
Origin and definition
Borrowing the title from the 1986 Steve Martin comedy, in the agile context Three Amigos means the continuous collaboration of
- Product Owners
in order to refine user stories and create acceptance criteria.
It's not strictly limited to these three parties, it is more about bringing different perspectives in as early as possible, resulting in higher quality requirements.
You don't want a Product Owner to make up acceptance criteria for user stories all on his or her own!
Conversations and shared understanding
The goal of the Three Amigos is not to produce artifacts like BDD tests or enhanced JIRA issues, it's more about creating a shared understanding and identifying problems early on. The Three Amigos work with user stories, which are first of all tokens representing the conversations happening about them.
So the value of The Three Amigos cannot be measured by the artifacts they produce. Of course this doesn't mean that creating artifacts is forbidden - just value the shared understanding more than the artifacts.
There are teams that only add stories to their sprints which have been "amigo-ed", making it part of the team's Definition-Of-Ready.
While the concept of a specification workshop exists (a meeting where Three Amigos work on user stories and refine acceptance criteria), it should rather be seen as a mindset - remember the corresponding agile principle
"Business people and developers must work together daily throughout the project."
Just like backlog grooming should be a continuous effort and not a regularly scheduled meeting, the Three Amigos should rather be seen as a pairing than a meeting - You actually do the work, not talk about it!