Already 8 years back a program called test craftsmanship program was introduced in my organization. Several other programs for craftsmanship have been started since and also other departments at Healthineers took over the approach.

But what is it about? Why do we use the term craftsmanship? Was it worth starting the programs?

First let us define craftsmanship. Then let's see how it went for test craftsmanship in the context of my department, what have been achievements and how we want to proceed here to ensure the sustainability.

Target Audience: Architects, Developers, Testers, Managers, Project Leader
Prerequisites:Basic Knowledge in software development in general
Level: Introductory

Tim is a developer who loves minimal solutions. Alex is anxious about quality. A while ago, Alex tried to get Tim on board with observability. She wasn't successful until a ticket escalated...

Since then, we unite our principles by proving to our customers that their software works (even better – is saving/making them money).

In this talk we’ll:

• tell you our stories of customer-centric quality
• show you metrics and dashboards we use

You’ll take away:

how to work with team and customer to improve quality by proving it works!

Target Audience: developers, testers, devops
Prerequisites:none
Level: Introductory

Extended Abstract:
It’s a story as old as time. Testers and developers trying to agree on what quality is and how to do it… Here’s our version.

Tim is a developer who loves minimal solutions. He knows quality is important, but he’s always looking for the most minimal way of doing it. Alex has the heart of a tester and has seen what kind of stuff goes wrong all the time. She’s anxious about quality.

A few years ago, Alex tried to get Tim on board with observability. How important it is for applications we manage for our customers. Her efforts weren’t particularly successful. Until one escalated ticket that led to us being up to our elbows in SQL statements searching for what had gone wrong. (Side note: nothing…).

On that day we had a realisation. Finding ways of proving to our customers that their software works (even better – is saving / making them money) is how we can unite our principles.

In this talk we’ll take you through the stories of how we got to our present state and we’ll show you what kinds of dashboards we create so our customers have access to their most important business metrics – and so that we can peek behind the scenes at anything going wrong.

You’ll take away ways of working *with* developers to improve quality for customers and ways of having conversations with customers to find out what their most important metrics are.