
Explore the fundamentals of agile software development and the agile manifesto, focusing on individuals and interactions, working software, customer collaboration, and responding to change to deliver value.
discover the whole-team approach in agile development: small, co-located cross-functional teams collaborate across developers, testers, architects, and business stakeholders, sharing responsibility for quality and product success.
Explore how agile projects use early and frequent feedback with short iterations and continuous integration, involving customers from the first sprint to prioritize and deliver high-value features.
Compare agile approaches XP, Scrum, and Kanban, including backlogs, sprints, product increments, and definitions of done, plus Kanban lead time and work-in-progress limits.
Explore continuous integration within agile testing, focusing on daily automated builds, integrated testing, rapid defect detection, and shared dashboards to ensure working, releasable software each sprint.
Refine the product backlog into user stories and define the release roadmap. Select stories in sprint planning (attrition planning), analyze risks, and estimate testing effort.
Explore sample questions from chapter 1 of the ISTQB agile tester foundation level course, focusing on agile manifesto values, interpretation, tester contributions, and retrospective practices.
Explore agile testing practices that deliver working software every sprint through short iterations, with customer feedback and shared ownership among developers, testers, and stakeholders.
Explore five independent testing options in agile, from on-demand external teams to long-term embedded testers, balancing independence with collaboration and specialized testing like performance, security, and other non-functional testing.
Learn to manage regression risk in agile projects by evolving manual and automated test cases, prioritizing automation at all levels, and maintaining an up-to-date regression suite with build verification test.
Clarify the tester's role in an agile team by driving collaboration, test coverage, and product quality across strategy, tools, environments, and defect resolution, while preserving independence in testing.
Explore sample questions on chapter two for the ISTQB agile tester foundation, covering agile test objectives, automation, exploratory testing, beta testing after iterations, and developer collaboration.
Explore test driven development, acceptance test driven development, and behavior driven development, explaining how tests drive code, acceptance criteria, and user stories, with collaboration across testers, developers, and business reps.
Compare the test pyramid in agile and traditional approaches, emphasizing early unit testing and automation, while reducing high-level tests, and highlight api and gui automated testing methods.
Explore the ISTQB testing quadrants, test levels, and testing types, detailing four quadrants from unit tests to operational acceptance and non-functional validation, manual or automated.
Explore the tester's role in agile teams, emphasizing cross-functional collaboration, empowered teams, visible Kanban boards, feedback-driven improvement, sprint zero setup, test planning, and continuous integration.
In agile projects, the team lists current-iteration backlog items and identifies quality risks, assessing impact and likelihood. Planning determines testing extent and techniques to mitigate project and product risks.
Discover how to estimate testing effort in agile projects based on content and risk, using planning poker and story points to derive reliable hours for product backlog items.
Understand acceptance criteria and adequate coverage, addressing functional behavior, non-functional quality characteristics, scenarios, business rules, external interfaces, data definitions, and definitions of done.
Apply acceptance test driven development by defining tests before development. Collaborate in a specification workshop to write positive, then negative and nonfunctional tests reflecting the user story.
Explore how exploratory testing fits within agile testing, using test charters and session-based management to quickly explore with limited documentation, uncovering defects and risks through focused, time-bound testing.
Explore task management and tracking tools for agile projects, from physical storyboards and sticky notes to Jiddah software, linking stories and tasks with estimates, dashboards, and traceability.
Explore how wikis, instant messaging, and desktop sharing enable lightweight, real-time communication and knowledge sharing for agile teams and distributed work, with tools like Confluence and Jira.
Explore software build and distribution tools that enable continuous integration and automatic deployment across environments, and support unit testing, static/dynamic analysis, documentation extraction and formatting, and manual quality assurance.
Explore configuration management tools that control versions and maintain history across requirements, test cases, defects, and code. Understand centralized and distributed version control for traceability in agile and traditional projects.
Explore test design, implementation, and execution tools in agile testing, including unit frameworks, test case management, test data generation, data load tools, automated execution, and exploratory testing capture of observations.
Explore cloud computing and virtualization tools for accessing remote servers and testing from different locations, and learn how snapshots capture configuration and network details.
Review sample questions from chapter 3 of ISTQB agile tester foundation level, covering test parameters, automation framework changes, risk analysis, planning poker, acceptance criteria, exploratory testing, and ALM tool features.
Agile testing is a relatively new approach to software testing that follows the principles of agile software development as outlined in the Agile Manifesto.
A tester on an Agile project will work differently than one working on a traditional project. Testers must understand the values and principles that underpin Agile projects, and how testers are an integral part of a whole-team approach together with developers and business representatives.
There is a lot of confusion concerning agile testing – which means there’s an educational opportunity as well. The Agile Tester will give the tester the knowledge to be part of agile testing teams and achieve high performance.
As a part of this course, you will be understanding the following learning objectives
The Fundamentals of Agile Software Development
The different agile approaches
The Differences between Testing in Traditional and Agile Approaches
Testing in Agile Projects
Roles and skills of a tester in Agile Projects
Agile testing techniques and methods
Assess product quality risks within an Agile project
Estimate testing effort based on iteration content and quality risks
Tools in Agile Projects
An Agile Tester can...
Collaborate in a cross-functional Agile team being familiar with principles and basic practices of Agile software development.
Adapt existing testing experience and knowledge to Agile values and principles.
Support the Agile team in planning test-related activities.
Apply relevant methods and techniques for testing in an Agile project.
Assist the Agile team in test automation activities.
Assist business stakeholders in defining understandable and testable user stories, scenarios, requirements, and acceptance criteria as appropriate.
Work and share information with other team members using effective communication styles and channels.