A role of Test Manager in Scrum

From your statement, integration and UAT testing are not part of the DoD for the programme; therefore, sprints do not result in items that are ready for production.

You are working with an imperfect version of Scrum. How you decide to manage the testing and release tasks is up to you. Ideally, these duties would be completed within the sprint.

It seems to me that the preservation of a "Test Manager" is simply preserving a non-Scrum role and reinforcing a phased development/testing approach. You will continue to be challenged with such questions and issues until you figure out a way to incorporate integration and UAT within the sprint, perhaps embedding such testers within each of the 8-9 Scrum teams?

> My query is on the role of test manager during
> product development, will he fit in with in
> scrum or will he be part of the shared service
> in scrum of scrums ...

From your reading of the Scrum Guide, do you think that test management should be handled by a Scrum Team or by another party? What are the 3 roles in Scrum? Which of them is responsible for developing an increment, and are sub-roles such as Test Manager allowed?

Must each increment that is developed be of release quality, or can there be outstanding work that is still left to be done, such as integration testing and UAT?

I totally understand that test manager doesn't fit in a scrum, I think I have to rephrase my query

We do a product development which has 8 to 9 scrum teams and before deploying this code in different region they need to be integrated with local systems for that region

Now when the core product uses scrum framework can't that be extended to the deployment as well for different region.

Then there would not be a need for a test manager

Ot may be this hybrid framework is for initial implementation and subsequent delta changes would use Agile in totality

Have any one of you come across this kind of scenario