Programme Launch Offer: Save 20% - Book Now

Track Talk, T16

Is TMMi Relevant in DevOps to Improve the Testing Process?

Szilard Szell

14:15 - 15:00 CEST, Tuesday 16th June

As a Test Coach we often ask ourselves what the next improvement is, or where to focus on. To “meet them where they are”, to know the current state, I usually assess organizations with a DevOps assessment, doing interviews and gemba “walks” with the different roles in the organization.

But when I want to go deep in how testing practices are followed, often I use Test Process Improvement models to make sure nothing is left out. One of the frequently used process improvement models is TMMi, but can it be used when the organization is Agile using DevOps practices (and culture)?

In this presentation I would like to share the exploration we have done in a TMMi task force, to see what alignments are needed to the TMMi model to utilise it in a DevOps organisation.

When we use TMMi within DevOps, we need to keep in mind to be practical, and relate the original practices into the context of DevOps: high level of automation, standardisation of work practices throughout cross-functional teams, utilisation of a CI/CD pipeline, and the balance between shift-left and shift-right practices.

For example, when we are looking for a written Test Policy, we might rather check what are the most important goals for the organisation related to deployment lead-time and frequency, as well as reliability.

When we are looking into test levels, we shall rather check the schema files of the CI/CD pipeline to understand the different testing jobs, and their purposes. When we are looking for shift left activities, we shall check what are mandatory checks in a pull-request. And when we are looking for Entry and Exit criteria, we shall rather check the DoR and DoD of the teams.