I need to ask why QA is a separate team if you know that would be
In Scrum, there is an expectation that the delivery team has all of
the people responsible for getting functionality for a product to
"potentially shippable product increment" state every sprint.
In order to accomplish this goal, the team needs to do the testing
activities necessary to meet their standard of quality to have
something that is shippable.
Can QA support the product teams in this arrangement? Given my
experience with other teams, I have not seen it work well. In fact, I
have found that QA is always a sprint behind (at least) from the team.
So, it strikes me as curious that the dev team is catching up. How
is that possible if there is new work to be tested?
Also, even if things are working pretty well is that sustainable for
the people in the QA team? How often do they task switch between
projects? How many hours do they work in each week? It sounds
pretty complex and chaotic the way you are describing their agility
I think many of your issues would go away if you integrated QA into
each of the product teams.
In addition, I am wondering if throwing it over to the wall for QA has
been working well for you? I have found that handoffs between teams
(and the processes/tools to support this) take more time than if the
teams were collocated working through the tests together. As well,
the fix and build cycles would be much less because the team is on the
same page on what needs to be fixed and work correctly.