ISTQB Certified Agile Tester

Explore agile's four values: individuals and interactions over processes and tools; working software over documentation; customer collaboration over contract negotiation; and responding to change over following a plan, shaping development.

Explore the 12 agile principles rooted in the four values, prioritizing customer satisfaction through early and continuous delivery of valuable software and frequent, working releases.

The whole team approach unites testers, developers, and business representatives to share quality ownership and collaborate in a co-located space with daily stand-up meetings.

Emphasizes early and frequent feedback in agile projects through short iterations and continuous customer input. Clarifies requirements, prioritizes high-value features, and uses sprint reviews to address issues early.

Explore extreme programming as an agile development and testing approach, alongside scrum and kanban, emphasizing communication, simplicity, feedback, courage, and respect to drive collaborative software delivery.

Visualize and optimize the flow of work with kanban boards, listing stages such as to-do, doing, and done, and manage work in progress to reduce lead time.

Collaborative user story creation emphasizes joint writing by product owners, testers, and developers, defining concise, testable acceptance criteria for functional and non-functional requirements. Apply the invest technique for clarity.

Retrospectives occur at the end of each iteration to review successes and failures, document improvements, and improve process, people, relationships, and tools through continual, cross-functional learning.

Discover how continuous integration in agile projects delivers a reliable product increment every sprint by automating builds, tests, and deployment, and by providing early, transparent feedback.

Explore agile release planning and iteration planning, refining the product backlog, splitting large stories, assessing risks, and aligning testers with acceptance criteria and Invest technique.

Plan iteration planning by selecting user stories from the release backlog, assess risk, estimate work via velocity, and define acceptance tests to guide testing efforts.

Explore how the ISTQB agile tester exam works, with immediate scoring, retry options, and detailed explanations, while reviewing scrum roles, the agile manifesto, and key values and principles.

Explore how the ISTQB certified agile tester emphasizes working software over documentation, delivering a time-to-market advantage, rapid customer feedback, and iterative delivery of valuable software.

Learn the whole team approach with shared workspace and face-to-face communication, and how evolving user stories affect iteration planning, product increments, and agile practices like retrospectives and continuous integration.

Explore extreme programming values: communication, simplicity, feedback, courage, and respect, and agile practices like early customer feedback, estimation extrapolation, and Scrum vs Kanban visualization and release approaches.

Clarify backlog refinement in scrum and distinguish product backlog, sprint backlog, and backlog refinement, with the product owner's role and sprints defined as iterations.

Explore how Kanban minimizes lead time and optimizes task flow through work in progress limits, while addressing specification problems, Invest criteria, and tester contributions to user stories.

Learn how testers drive test related improvements in retrospectives by proposing static analysis, code reviews, automation, and clear acceptance criteria, while evaluating continuous integration benefits and challenges.

Describe how risk analysis informs both release planning and iteration planning, and how to define testable user stories with acceptance criteria, then break them into testing tasks and test levels.

Compare testing in traditional waterfall and agile projects, noting differences in epics and user stories, continuous testing, cross-functional scrum teams, risk-based planning, and automation.

Balance business, development, and testing work products to deliver value-driven software; prioritize user stories, acceptance criteria, automated unit tests, lightweight tester artifacts, and documentation.

Explore unit, integration, system, and acceptance testing in agile projects, highlighting overlap, entry and exit criteria, automated verification testing, manual validation testing, and the role of business stakeholders.

Agile teams manage configuration with automated build and test frameworks, running static analysis, unit tests, and code coverage on every check-in to ensure a stable, installable build.

Explore independent testing options in agile projects, including testers within the team in scrum, on-demand independent teams, and long-term independent separatist teams, balancing unbiased evaluation with independence risks.

Track testing progress in agile projects with burndown charts and an agile task board. Use daily standups to surface blockers, verify acceptance criteria, and gauge satisfaction through customer feedback.

Manage regression risks in agile projects by implementing test automation across unit, integration, and acceptance tests, and refactoring test cases as features change.

Discover the roles and skills of an agile tester, including test automation, tdd, atdd, and white-box to black-box testing. Learn collaboration, test coverage reporting, and independence in a cross-functional team.

Learn how acceptance testing occurs at iteration boundaries, differentiate future validation testing from feature verification testing, and apply agile testing flows including unit tests, future acceptance tests, and build verification.

Assess the advantages and drawbacks of fully independent test teams in agile projects, while exploring test case refactoring, collaboration with developers, and effective metrics for quality.

Shows that a user story represents business requirements specifications, not BRD or test artifacts, and covers agile testing techniques, invest technique, and acceptance test driven development.

Explore how low level design specifications relate to test cases, and how agile testing emphasizes overlapping test levels, definitions of ready and done, and regression testing across iterations.

Automate static analysis, code coverage, and unit tests at code check-in, schedule functional tests every few days, and use real-time test reporting to identify defects.