Typical starting situation
We often find the following picture: tests are planned ad hoc, every team tests differently, and a consolidated risk assessment is missing. Critical releases are postponed because defects surface massively during the pilot phase. The business units lose trust, and the executive board demands a change of course.
The typical assignment we receive: a reliable test process with risk-based control within a few weeks, without jeopardizing the next release.
How we typically proceed
Twelve weeks, five clear steps – one senior consultant as interim test manager in the program:
- Maturity audit and workshop (weeks 1–2) – TMMi-oriented assessment across all test teams, a shared view of the biggest weak points.
- Risk-based test strategy (weeks 3–5) – a risk-coverage matrix per product, clear test-scope decisions with the business unit and architecture.
- Test process standardization (weeks 5–7) – consistent templates for test plans, defect reports and acceptance criteria.
- Reporting dashboard (weeks 7–9) – live status per release, automated reporting for the executive board and business units.
- Training and coaching (weeks 9–12) – enabling the test teams, with coaching during the next live release as a safety net.
Typical impact figures
These are the orders of magnitude we typically see a few months after the end of an engagement in comparable mandates:
Range varies depending on the starting situation. We clarify reliable expected values for your case in the Quick-Check.
Typical engagement framework
