← Back to Insights Quality Assurance · Test Management

Test Management: Tasks, Role and Process in IT Projects

30 October 2026 · Ramin Amini

Many projects test a lot but steer very little. Test cases are created in different teams, defects sit in several lists, and shortly before go-live nobody knows exactly how well the software has actually been tested. Test management closes this gap. This article explains what test management covers, which tasks a test manager takes on and how to set it up effectively in both traditional and agile projects.

What is test management?

Test management covers the planning, control and monitoring of all test activities in a project or programme. It ensures that the right things are tested at the right time, that results are documented traceably and that release decisions are based on reliable information.

It helps to distinguish it from related terms:

• Quality assurance is broader. Besides testing, it includes preventive measures such as reviews, coding guidelines and clear requirements.
• Test strategy and test plan are documents. The test strategy describes how testing is done in principle, the test plan makes this concrete for one project. Test management is the activity that creates both, puts them into practice and adapts them continuously.
• Testing itself, i.e. designing and executing test cases, is the operational work that test management plans and coordinates.

Test management tasks along the test process

The ISTQB test process consists of test planning, test monitoring and control, test analysis, test design, test implementation, test execution and test completion. Test management is primarily responsible for the framework: planning, control and completion.

Test planning

It starts with the question of what will be tested and what deliberately will not. This determines test levels, test types, test environments, test data, roles, dates and exit criteria. Priorities follow risk: areas whose failure would be costly in operation are tested first and most thoroughly. The article Risk-Based Testing shows how this works in practice.

Test control and test monitoring

No test plan survives reality unchanged. Deliveries arrive late, test environments go down, critical defects block entire test areas. Test management continuously compares plan and actual progress, spots deviations early and takes corrective action: shifting priorities, reallocating resources and reporting risks to project management.

Defect management

Defects are only valuable if they are handled reliably. Test management defines how defects are logged, rated by severity and priority, assigned and retested after the fix. A short, regular triage meeting with development and the business side prevents critical defects from getting lost in long lists.

Test reports and release recommendation

Stakeholders do not need lists of test cases but a clear statement: how far along are we, which risks remain, and can we release? A good test report answers exactly these questions and ends with a well-founded release recommendation. The actual decision is made by the project or the business side, for example as part of acceptance testing.

Test completion

After the release, testware is archived or handed over for maintenance, open defects are documented and lessons learned are recorded. What worked well, where were there delays? These lessons feed into the next release and improve the test process with every iteration.

The role of the test manager

A test manager needs methodological knowledge, but above all overview and strong communication skills. They translate between development, the business side, operations and project management and represent the quality perspective even when schedule pressure rises.

• Test manager vs. tester: Testers design and execute test cases. The test manager plans, prioritises and makes sure the work of all testers fits together.
• Test manager vs. project manager: The project manager is responsible for the schedule, budget and scope of the whole project. The test manager provides the quality information on which they base their decisions.
• Independence: A test manager should be able to speak openly about risks without their report being tied to project goals they have to meet themselves.

How quality assurance fits sensibly into the project plan is also described on our page on IT project management in Hamburg.

Test management metrics: few, but meaningful

Metrics should support decisions, not document busyness. A small set of values, reviewed regularly and over time, has proven effective:

• Test progress: planned, executed, passed and failed test cases, ideally split by risk class.
• Requirements coverage: which requirements are covered by tests, and which of them have been verified successfully?
• Defect status: open defects by severity and status, and the trend over time.
• Blockers: defects or environment problems that hold up entire test areas.

Be careful with numbers without context: a high number of executed test cases says little if the critical business processes have not yet been tested. What matters is always what a metric says about the remaining risk.

Test management tools: the tool follows the process

Tools such as Jira with Xray or Zephyr, TestRail or Azure Test Plans help manage test cases, test runs and defects and link them to requirements. But they do not replace a process. Before introducing a tool, be clear about which information should end up in the test report. From that you can derive the structure the tool needs. A lean structure that is maintained consistently is worth more than an extensive setup that nobody keeps up to date. Automated tests, such as automated regression tests, should feed their results into the same overview.

Test management in agile projects

Scrum teams have no separate test manager role; responsibility for quality lies with the whole team. The tasks of test management do not disappear, they are distributed: test planning happens in refinement and sprint planning, test control via the daily and the board, test reporting through the Definition of Done and the sprint review. Read more in Agile Testing in Scrum Teams.

As soon as several teams work on one product, interfaces to other systems exist or releases require formal approval, cross-team coordination is still needed. An agile test manager then works across teams: they ensure a shared test strategy, plan integration and end-to-end tests across team boundaries and support the teams as a coach.

Common mistakes in test management

• Planning testing only at the end: If test management is involved shortly before go-live, test environments, test data and testable requirements are missing.
• Reports without a message: Tables full of numbers do not help if they are not followed by an assessment of risks and release readiness.
• Defects without owners: A defect without a responsible person and without a priority stays where it is.
• Plan not adapted: A test plan that ignores delays creates a false sense of security.
• Tool instead of process: A new tool does not resolve unclear responsibilities.

Conclusion

Test management turns many individual test activities into a process that can be steered. It plans based on risk, keeps track of progress and defects, takes corrective action when things deviate and provides a clear basis for the release decision. Whether as a dedicated role in a large project or distributed across agile teams: what matters is that someone keeps the overview and makes quality visible before the software goes live.

Frequently asked questions about test management

What does a test manager do?

A test manager plans the testing of a project, prioritises it by risk, coordinates testers and stakeholders, monitors test progress and defect status and reports regularly to project management and the business side. At the end, they give a well-founded release recommendation.

What is the difference between test management and quality assurance?

Quality assurance covers all measures that safeguard software quality, including reviews, guidelines and clear requirements. Test management is part of it and focuses on planning, controlling and evaluating the tests.

Which certification is available for test managers?

The ISTQB scheme is widely used: the Advanced Level Test Management builds on the Foundation Level and specifically covers test planning, test control, risk management and leading test teams. Practical project experience remains at least as important as the certificate.