Skip to main content

QA Strategy

ISTQB® Agile Tester: Building Quality into Agile Teams

In agile teams, quality is everyone's job. What the ISTQB® Agile Tester certification covers and how it helps in Scrum projects.

What is the ISTQB® Agile Tester certification?

The ISTQB® Foundation Level Agile Tester (CTFL-AT) is an extension of the Foundation Level. It covers how testing works in agile projects – in line with the values and principles of the Agile Manifesto.

Franz Hetz passed the certification on 1 March 2024, a few days after the Foundation Level. Together they form the basis for quality assurance in Scrum, Kanban and other agile frameworks.

Why testing is different in an agile team

In traditional projects, testing follows at the end of development. Agile projects have no such "end": software is built in short iterations, requirements change, and every iteration should deliver a shippable result.

This fundamentally changes the tester's role. Instead of finding defects after development, the tester helps prevent them in the first place. Quality becomes the responsibility of the whole team – development, business and testing work on it together (the whole-team approach).

What the certification covers

  • Agile fundamentals: the Agile Manifesto, Scrum and Kanban, roles and events – and where testing fits in.
  • User stories and acceptance criteria: how to phrase requirements together with the business so they are understandable and testable.
  • Test pyramid and testing quadrants: which tests make sense at which level and what should be automated.
  • Test-driven approaches: TDD, ATDD and BDD – tests as a specification before code is written.
  • Exploratory testing: structured exploration of the software, complementing prepared test cases.
  • Continuous integration: how automated tests in the CI pipeline provide fast feedback.

An example from the sprint

A typical user story reads: "As a customer, I want to be able to reset my password." Without acceptance criteria, every team member understands something different by it. During refinement, the tester therefore asks:

  • How long is the link in the email valid – and what happens afterwards?
  • What does someone see who enters an unregistered email address? (For security reasons, the message should be the same as for a registered address.)
  • What requirements apply to the new password?
  • Can the flow be completed by keyboard and with a screen reader?

The answers become acceptance criteria, often in the "Given … When … Then …" format. They serve as a specification for the developers and can be implemented directly as automated tests. At the end of the sprint it is clear when the story is done – without debate at acceptance.

These ten minutes in refinement often save days of rework: questions that would otherwise only surface in testing or after release are answered before the first line of code is written.

How we apply this knowledge in projects

Most software projects today are run in an agile way. In practice, this means for the collaboration:

  • Involved early: user stories are checked for testability and acceptance criteria are sharpened during refinement.
  • Testing within the sprint: new features are tested in the same iteration in which they are built – not in the next release.
  • Risk-based prioritisation: when time is short, testing starts where a defect would cost the most.
  • Automation with a sense of proportion: recurring checks go into the pipeline, exploratory tests where human judgement is needed.

The result is releases that stay predictable even when requirements change.

Frequently asked questions

What is the difference between CTFL and CTFL-AT?

The Foundation Level (CTFL) covers the general fundamentals of testing. The Agile Tester extension (CTFL-AT) builds on it and shows how these fundamentals are applied in agile teams.

Do agile teams need dedicated testers at all?

Quality is everyone's job in an agile team. An experienced tester, however, brings methods that are often missing day to day: systematic test design, risk-based prioritisation and the perspective of the future user.

What is the test pyramid?

A model showing how tests should be distributed: many fast unit tests at the base, fewer integration tests in the middle and a small number of costly end-to-end tests at the top.

What makes good acceptance criteria?

Acceptance criteria describe concretely and verifiably when a user story is done. Good criteria are unambiguous, written from the user's perspective and translate directly into test cases.

Verification

The certificate was issued by iSQI under ID 24-CTFL-AT-241517-01 and can be verified publicly: View credential on SkillsClub (opens in a new tab).

Industries

Industry expertise

Every industry has its own rules, risks and auditors. We know them from practice – and test so that your software not only works but stands up to every audit.

  • Financial services

    Online banking, core banking systems and regulated processes. We test against high security and compliance requirements – so releases stay predictable, traceable and auditable.

    • BFSG
    • DORA
    • BAIT
  • Public sector

    Specialist applications, citizen portals and SAP landscapes. Accessibility under BITV, clean acceptance testing and documentation that stands up to any audit.

    • BITV 2.0
    • EN 301 549
    • SAP
  • IT & Software

    For software vendors and IT service providers: test strategy, automation in the CI/CD pipeline and quality assurance of AI features – from MVP to release.

    • CI/CD
    • Test automation
    • EU AI Act