My Product Team has a centralized QA team with a QA Team Lead. Currently, we are going through restructuration, which will distribute the QA team members among 4 existing dev teams: each team will have X developers and 1 dedicated QA engineer.

  1. Is the QA Team Lead role still needed in this new structure?
  2. If so, how does the new team structure impact the role of the QA Team Lead?
  • 1
    btw, really good testing - the kind that a truly modern agile team would have - requires more than a 1:n arrangement of qa to dev. With only 1 tester (and thus also an immediate bus factor) this arrangement will force the role to be very limited. This is a typical approach for companies going thru agile transformations. It's really hard to change and the testing area needs big change that is really really hard. Commented Apr 8, 2021 at 14:15
  • For example for some tickets, the testing part might take longer than the development part. How can high quality be promoted with that sort of set-up ? Commented Apr 8, 2021 at 14:17

2 Answers 2


The QA team lead will often remain but their role should change considerably.

They will now focus on supporting the individuals instead of a project

Instead of being focused on specific current project topics, issues and deadlines the lead should switch to a role that supports the employee more generally in terms of skills development and career advancement, as well as engaging senior management in support of these goals.

What you will hear a lot for this change (as already indicated in your question title) is that management is now "cross-functional". This means that for project specific issues you are effectively 'reporting to' to the project owner or lead (actually to the team is a better approach). For employee specific issues such as career training, promotion, etc. you use a QA lead.

The team lead is likely to find this quite hard. They are essentially going from a 'supervisory' to a 'support and encourage' role and this requires really different skill sets and approach. Many companies miss this and end up not actually changing their organization, just using names such as 'stand-up', 'retro', 'backlog grooming' to persuade themselves that they have changed but outside of those ceremonies the practices throughout the day may not have changed. Change is really hard and change from supervisor to councilor is one of the hardest.

They will also focus on new aspects such as test training, cross-training, etc. which will allow the lead to use folks more interchangeably in more of an 'internal consulting model' allowing for both more flexibility to meet team needs as well as more opportunity to learn and grow for individuals who want it.

Finally, the team lead can focus more on the organizational goals for quality and spend more time engaging senior management to get the support and backing for quality goals and initiatives.


It really depends on the company, culture and mainly the goal of this change.

Ideally I don't see a need for a QA Team Lead role, following a successful role shift the tester in the team becomes an enabler and accelerator and no longer the only one concerned about testing and quality. As such there is no need for a centralized Test Team Leadership because the responsibility for testing moved to the whole team and its lead.

Some examples for an enabler and accelerator role could be building automated test infrastructure and educating the team about adding tests to it, coach and review tests developed by team members or enhance the teams general testing related knowledge.

Having said that you should be aware the it is not an easy transformation. Being a lone tester in such a team requires the right skills, both soft and hard skills, but in your case of a small team you "inherit" a set of testers and can't control their skill level. This means that for the short run a central role might be beneficial. At this role the lead will simply take part of the accelerate and enable part on himself while coaching the testers to be independent, or in other words the lead will try to decommission himself...

  • 1
    Good answer. The main issue I have experienced in real world engagements is that many folks, especially devs, already have a very fixed idea of what 'QA" means and do not expect them to be empowered. I've even seen posts here stating that qa is just a route to being an app dev. Wrong. In so many ways. But you have to allow for others perceptions in trying to change them. Also for the fact that QA folks themselves are often folks picked for the former model and over time have learned to become subservient in order to survive and fulfill the role presented to them as post-development verifiers Commented Apr 8, 2021 at 12:45
  • In one place I've worked for (one of those American giants) they simply announced that everyone are developers starting from a specific date, no exceptions no transition time, in other places it's a long and winding journey
    – Rsf
    Commented Apr 8, 2021 at 13:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.