About

How TSC started #

TSC began with an invitation. After time in local government, followed by a few years with a software testing consultancy, a former colleague asked for a return to lead software quality assurance on a major programme. They had asked more than once, and this time the timing was right.

We bring the same approach to every engagement: start from the highest risks, find problems early, and leave teams stronger than when we arrived.

Who’s behind it #

TSC is a one-person business, and that person is Nathan. The approach and values are TSC’s, but the experience behind them is mine.

My working life began in a corporate role more than 30 years ago and has taken me through a wide range of roles and industries since. Much of it was business process improvement and keeping business systems running well. For more than 10 years now, I’ve worked in software delivery as a tester, test lead and BI business analyst. I’ve held nearly every role in the delivery lifecycle except developer, so I understand both the business problem and the technical solution, and I know where the gaps between roles tend to appear.

Three storeys, one story #

Quality has to hold up at every level of a delivery. Each level has a role in getting the story finished.

Strategic: setting the plot #

Test strategy, quality goals, and clear advice for senior stakeholders on risk and readiness.

Tactical: structuring the chapters #

Test plans, approach, resourcing, reporting, and the processes and tools that turn the strategy into something workable.

Operational: seeing it through to the last page #

Designing and running tests, managing defects, and delivering test cycles through to sign-off.

We work across all three, so what’s decided at the top is what gets tested at the bottom, and what’s found at the bottom reaches the top.