At first glance, Scrum doesn't say anything about how to test and who should take responsibility for it.
Sure, it is always said that in Scrum the team is testing. But who bears the responsibility?
If you look at the standards of the ISTQB, a test manager has tasks like
- the creation of a test team,
- the creation of a test concept,
- Creation of test cases by the testers,
- Creation and execution of test cases by the test team,
- and much more (see below)
How does an agile test process fit into this, which doesn't prescribe all this?
The testers in the team - or rather the development team itself - are now confronted with these things and the competence of the testers grows because they have to cover the entire test pyramid. This means that the testers are now responsible for unit, service and system testing and have to master testing, domain and coding, as they should automate all tests, if not have to.
The question is which test organization, apart from agile testing the test manager should take over. According to ISTQB, he takes over the conception of the processes and the management of the testers.
But the Scrum process does not define exactly that!
Even after studying the roles of Scrum, it is not clear: Who takes over the tasks of the test manager? or how they are distributed? In order to answer the questions, it is first necessary to determine which tasks a test manager performs in the classic test and quality assurance process.
According to the International Software Testing Qualifications Board (ISTQB), the certification body for testers, the tasks and areas of application of the test manager go beyond the control of the test project. He manages the test department or the test team and thus the resources for the tests.
He prepares reports, escalates to development, technical department and project management, assesses test projects, enforces compliance with the company's quality processes and procedures, procures the testing tools for the organization and reviews the test plans and test cases.
Are there clear guidelines on how the test manager should organize himself inside or outside the agile process?
I ask this question consciously here and not in the Scrum area!
I find that these questions are not a classic Scrum topic in themselves, but a special topic between both aspects, but more in the direction of test management organization.
Is this division of tasks, therefore, more strategic and operational?