This method aims to :
- design new features in the best possible way.
- ensure shared understanding of the feature.
I discovered this method a few years ago, and I was quickly won over. But before explaining in details who are these “3 amigos”, it may be better to analyze the default “watefall” process.
The default “watefall” process
The waterfall process is a simplified version of the “V cycle” methodology. It is a sequential process which can be broken down into 3 phases :
- design of the feature : the Product Owner (PO) collects needs from his customers, then imagines a feature to meet these needs. This feature is then described in a (more or less) long and detailed specification, eventually with visual examples (Marvel, Figma, etc.).
- implementation of the feature : the feature specification is given to the development team. Sometimes, there can be a kick-off meeting (with developers and product team) to officially launch the implementation. The developers then implement the feature. Once it is done, the feature is sent to QA.
- test of the feature : the QA takes note of the specification, then tests the feature implemented by the developers. If everything is OK, the feature can be released. If QA finds bugs, it sends back the ticket to the developers, who will fix (or not) the QA feedbacks. Once done, the devs send the feature back to QA, and we start over until release into production.
With this process, we can easily find out some issues that can create friction or slowness :
- QA is not always included in the discussions during the feature design : QA cannot therefore discuss in advance the tests that need to be carried out, nor warn about scenarios that would have been forgotten by the product team.
- Following previous point, QA can also misinterpret the specification and then run irrelevant test cases.
- The developer cannot say anything about the designed solution : his role is then limited to a “mere performer”.
- During its tests, the QA may think that behavior is not the expected one. He will then discuss with the developers and / or the PO. In case the QA is right, the developer will have to rework the behavior (rework ==> loss of time). In the other case, it will represent a loss of time during discussions (and eventually with the change of focus.)
To get rid of these issues, the “3 amigos” are there for you!
The “3 amigos”
This method relies upon 2 pillars in my opinion:
- put together, as soon as possible, our 3 friends: PO, dev, QA (hence the name of the method)
- for the PO, have a precise, but eventually not definitive, idea of the feature to be implemented
This ceremony should be initiated during the specification, and before the start of implementation. It allows to solve the majority of the issues we found during the waterfall process. In addition, it happens quite often that the solution the PO imagined differs slightly with the one defined at the end of the meeting: by putting everyone together, each entity will bring its expertise, propose evolutions which simplify life of each, and thus allow the best feature to be created at the lowest cost.
- PO provides the added value of the product: he knows what are the real needs, and can therefore choose the best solution to meet them
- Dev is the technical entity: he knows what will be easy (or not) to implement, and will be able to propose to the PO equivalent costless solutions. He can also estimate the workload and thus alert if the ratio (added value / cost) becomes too low
- QA provides the test part: he searches for all the weird usecases, and can already show which tests will have to be done, so that the developer can already take them into account, or even test them himself during development. He can also remind about the testability of the feature.
The main goal of this ceremony is to allow a better communication between people who are often separated. It allows a shared understanding of the feature, while minimizing the risks of rework, due to poor specification. Finally, note that this is a real application of one of the precepts of the agile manifesto “Individuals and interactions over processes and tools”: https://agilemanifesto.org/
What you must remember
- Waterfall process isolates QA, limits its contribution, and creates slowdowns and frustrations
- the “3 amigos” process
- includes PO, dev, QA
- aims to rework / complete the specification of the PO
- allows a shared and complete understanding of the feature
I am really impressed with your writing skills and also with the layout on your
weblog. Is this a paid theme or did you modify it yourself?
Either way keep up the nice quality writing, it’s rare to see
a nice blog like this one today.
Feel free to visit my web blog :: Royal CBD
Thank you very much for your comment !
It is not a paid theme, it is the Maxwell theme, which has is partially free, and can be customized quite easily.
I’ll look at your blog very soon.
That is a great tip especially to those new to the blogosphere.
Simple but very accurate information… Thanks for sharing this one.
A must read post!
Thank you very much, don’t hesitate to share it on social networks if you find it interesting !
Excellent, what a web site it is! This weblog provides valuable facts to us,
keep it up.
Thank you very much, I’ll continue publishing new posts soon as the holidays are over
Hello just wanted to give you a quick heads up and let you know a few of the pictures aren’t loading correctly.
I’m not sure why but I think its a linking issue. I’ve tried it in two
different internet browsers and both show the same outcome.
OK, thanks for the feedback, I’ll try to understand what is going on and fix this soon
I know this if off topic but I’m looking into starting my own weblog and was wondering what all is needed to get setup?
I’m assuming having a blog like yours would cost a pretty penny?
I’m not very web savvy so I’m not 100% certain. Any suggestions or advice would be greatly appreciated.
Cheers
Also visit my website … Peter
I was also quite scared at the beginning, but in fact, it is quite easy to create your own weblog : I used wordpress, and there are many free themes that you can customize as you want. Also, you have to pay (annual billing) for the host of your domain, with a domain provider. There are many tutorials on internet with detailed procedure to understand how to do that, as https://www.wpbeginner.com/guides/ for instance
A+ Fast shipping, great customer service!!!
Perfect !!! no issues at al.
Thanks for your comment !
GREAT PRODUCT. recipient loved it!
Thank you very much
Good luck, hope this review helps you in your decision.
Thanks !
Hi there, yeah this post is truly nice and I have learned lot of things from it concerning blogging.
thanks.
Have a look at my site: blog, Michaela,
Helpful information. Lucky me I found your website by accident, and I am shocked why this accident didn’t happened in advance!
I bookmarked it.
Take a look at my web site – Angeles
Marvelous, what a website it is! This website presents useful
facts to us, keep it up.
Have a look at my page … Faye
Thank you for the auspicious writeup. It in fact was a amusement account it. Look advanced to far added agreeable from you! However, how can we communicate?|
Thanks again for the blog post.Really thank you! Fantastic.