Traditional QA team
Id let to get some opinions on what a Traditional QA team should be.
The specifics like team number and nice to have personality types as well would be most appreciated.
If you have unlimited budget, make sure you have 1 QA for every developer. QA Engineers should be inquisitive, skeptical, thorough, passionate and always looking to improve the quality of the application.
My ASQ Certified Software Quality Engineer (CSQE) Certification training batch is starting on July 11 2016. Details and 6 VERIFIABLE RECOMMENDATIONS for my training at www.facebook.com/PickTechnologies
All teams are different. But if I were composing a team from scratch and assuming some sort of Scaled Agile Framework like process, my team composition would probably be...
1 product test lead. This test lead would be responsible for triage, test strategy, and planning major releases. This skills you're looking for here is someone who is quantitative and strategic. He'll be setting the high level strategy / test planning, and he needs to be able to adapt the plan according to business needs and the situation. Person needs to be highly quantitative because they'll be providing a lot of estimates and need to be able to make accurate estimates that business planning relies on.
1 Sr. QA Engineer for every for each large functional group. Say your dev teams there's a backend team, a front end team, a mobile team, and a platform team. You'll want 4 Sr. QA Engineers. The reason you'll want Sr. QA Engineers is you'll need to delegate the majority of the low level test planning and need domain experts in their respective areas to supervise and review work from other testers. Traits to look for are experienced professionals that have strong analytic skills to analyze requirements and changes and write feature test plans efficiently for every release.
1 mid/jr level QA Engineer to about 2-3 developers (for manual heavy, 5-6 to 1 for automation heavy process). 2 developers to 1 QA ratio works great in that you can have 2 scrum teams on 2 week cycles offset, which will give you a QA ready build every week from alternating teams, and QA bandwidth will keep pace with amount of new code created. Here your'e looking for people with a high learning potential, and attention to details.
1 SDET/SET for every 5 developers. SDET and SETS are largely responsible for test automation. A 1 to 5 ratio let's you your SDET and SET be on the winning side of the 80/20 rule. They can produce about 20% the amount of code as the developers, but cover around 80% of the functionality because they are writing tests end-to-end as oppose to module level. You're looking for high technical knowledge and very organized as they'll be writing a lot of code. Test code is very hard to maintain, so having someone that is very organized is very helpful to maintain velocity as test code base grows.
1 Load Testing expert per every 6-10 backend/database developers. This is mainly to provide some light amount of load testing coverage to keep pace with the major releases, but not test every single minor release. You're looking for moderate technical knowledge and high platform experience. Working with distributed load testing rigs can be very tricky.
Last edited by dlai; 03-16-2016 at 06:50 PM.