My Workshops

Interactive workshops about software testing, agile and quality

About my workshops

I regularly deliver workshops on software testing, quality and testing skills. My workshops are hands-on and interactive: participants dive straight into exercises, discussions and real-world cases. No endless PowerPoints, but active learning by doing.

I deliver these workshops through Cerios, together with my fellow consultants and trainers. We provide workshops on-site at organizations, as part of conferences, or as open enrollment through Cerios Academy.

Interested in a workshop for your team or organization? Or would you like to know more about the possibilities? Feel free to get in touch!

Testing and Quality, A test retrospective and risk session with your team

In this workshop I explore with your team what testing and quality means in your context. Using the Agile Test Model, we investigate where quality originates: from customer needs and requirements all the way to the product. As a team you reflect on your current way of working and we conduct a test retrospective. We map out what is already going well, what can be improved and what is still missing in terms of testing and quality control. The second part of the workshop focuses on discovering risks. We use a technique called Risk Mining, based on quality characteristics from ISO 25010. We identify and prioritise your most important product risks. The result is a shared quality picture, concrete improvement actions and clear focus areas for testing and development.

Test Design Techniques – better coverage with fewer test cases

This workshop focuses on applying test design techniques to test more effectively and purposefully. Participants learn the difference between test methodologies, test levels, test types and test design techniques, and how these fit within agile software development. The emphasis is on making conscious choices: what do you test, what do you not test, and why?

Using recognizable examples and exercises, participants work with techniques such as equivalence partitioning, boundary value analysis, CRUD, process and path testing, and decision tables. The workshop shows how test design techniques help create fewer test cases while actually increasing content coverage and quality.

Duration: 3 to 4 hours

For whom:

  • Testers who want to deepen their craft
  • Teams who want to test more consistently and purposefully
  • Anyone who wants more grip on test coverage and risks

What you will gain:

  • More effective use of test design techniques
  • Fewer test cases, more value
  • Better justification of test choices

The Many Flavours of Risk Sessions – From Risk Thinking to Focused Action

Keywords: risk sessions workshop, risk-based testing, risk mining, bowtie analysis, ISO 25010

In this workshop, participants learn how to identify and map risks around software and products in a structured and effective way. No single method is central; instead, we use multiple forms of risk sessions, each with its own purpose and moment of use. The workshop shows why risk-based testing is essential in complex environments where you can never test everything and where assumptions, biases and time pressure play a major role.

Participants experience and practice different techniques such as the Nightmare Headline Game, Risk Mining and the Bowtie risk analysis. We use ISO 25010 quality characteristics to look at risks beyond just functionality and security. The focus is on collaboration, dialogue, and translating risks into concrete testing and control measures. The result: sharper priorities, better decision-making and more grip on quality and value.

Duration: ⏱ 3 to 4 hours

Who is it for:

  • Testers and test coaches
  • Product owners and business analysts
  • Developers and agile teams
  • Anyone involved in risk and quality decisions

What you get:

  • Insight into different types of risk sessions and when to use them
  • A concrete overview of product risks and priorities
  • Practical techniques to translate risks into test focus and measures

Do the Bughunt! – testing together with stakeholders

Keywords: bughunt workshop, exploratory testing, collaborative testing, user acceptance, agile testing

A bughunt is an interactive and energetic way to test software together with stakeholders, users and team members. In this workshop participants learn what a bughunt is, why to use it, and how it fits within exploratory testing and the Agile Test Model. A bughunt breaks the autopilot, brings fresh perspectives and quickly creates insight into the quality of new or existing functionality.

Participants experience how to prepare and run a bughunt: from writing test charters and assigning roles to running the bughunt as a game element. With the help of a bug board, light competition and a joint debrief, a shared understanding of the application and its risks emerges. The workshop shows how a bughunt not only finds bugs, but also strengthens collaboration, knowledge sharing and engagement.

Duration: ⏱ 3 to 4 hours

Who is it for:

  • Testers and agile teams
  • Product owners and stakeholders
  • Users who want to be actively involved in quality

What you get:

  • Fast and broad feedback on software quality
  • More engagement and shared understanding among stakeholders
  • A practical format to run bughunts independently

Exploratory Testing – working with test charters

Exploratory testing is a powerful testing approach where learning, test design and test execution come together continuously. In this workshop, participants learn how to apply exploratory testing in a focused and professional way using test charters. No aimless "clicking around", but structured exploration with clear goals, focus areas and expected information. The workshop demonstrates why exploratory testing is essential alongside automated and scripted testing, especially in complex and changing environments.

Participants work hands-on with testing tours, creating effective test charters and documenting and discussing findings using lightweight structures like BRIEF. The workshop helps testers and teams discover product risks faster, ask better questions and make the value of testing visible to stakeholders.

Duration: 3 to 4 hours

For whom:

  • Testers (junior to senior)
  • Agile teams
  • Test coordinators and test coaches

What you will gain:

  • More structure and focus in exploratory testing
  • Better risk recognition
  • Insight into making your test work visible and discussable