Back to Knowledge Base
    CasesJan 9, 2025

    Case: A Testerless Team

    A senior team modernizing a company's wage engine - exploring whether they needed a tester and what profile that tester should have.

    Case: A Testerless Team

    This team was under serious pressure.

    Their job: modernise the company's wage engine. Not just any system. THE system. The beating heart. The money machine.

    They were using the strangler pattern, building a new engine alongside the old one. The plan was to swap them out when the new one could handle everything. It wouldn't be a copy though. It had to be faster. Better. The usual expectations.

    The team was stacked with senior people who'd been there for years. Everyone wanted in, so they got their pick of the best.

    I came in to answer one question: do they need a tester? And if so, what kind?

    Two very different perspectives

    The team had 3 full-time functional analysts, 4 developers, a product owner, and a scrum master.

    The analysts were scared. Scared of failure. Scared of looking bad. Scared of getting something wrong.

    They told me 60% of their time went to verifying engine output.

    Their view: any tester without their background would take months, maybe years, to be useful.

    The developers? Less worried. They trusted their unit tests. They trusted their fail-safes.

    What the RiskStorming session revealed

    We gathered everyone in the afternoon and worked through it together.

    Quality aspects. Risks identified. Standard stuff so far, but valuable for alignment.

    Then I did something different in the third phase.

    I held back the 'Tester mitigation activity' cards. First, they mapped what they were already doing from their own roles to address the risks.

    Then I handed them the tester cards. I asked them to mark which activities they were already covering.

    Then the key move: add any activities from the deck that weren't being done but would help. But place them sideways on the board.

    Now they could see it clearly. Which activities a tester could take over. What new value a tester would bring.

    They walked out knowing exactly what profile they needed, how that person would help, and had the raw material for a job description.