Language menu for mobile

Testing in Agile Development

Most Agile discussion now focuses on practices, with Scrum, for managing product development, and eXtreme Programming (XP), for software development practices, being the most common. Both Scrum and XP exclude traditional Software Testing from their practices. So, how and where does the Test Engineer/traditional testing fit in? In this class, we offer effective strategies and tactics, specific test practices, experience, and possible points-of-conflict so that the test team can successfully support the goals of Agile development and provide the most effective technical service to the product team.


This training course provides effective strategies and tactics to support the goals of Agile development. The course will start with the essential understandings of Agile—for example, people over process—that impact the everyday work of test teams. From there, most of the class will focus on how traditional test teams provide value and how they fit into Agile projects,

This includes:

  • New planning activities

  • New test strategies

  • An increased volume of code

  • Faster code deployment

  • Different ideas on test artifacts

  • New ideas on Test Automation

  • Different issues with offshore and outsourced teams

  • Examples, exercises, and mini-Scrums

Who Should Attend?

Software Testers, Business Analysts, Test Managers, QA Specialists, Scrum Teams, and Test Engineers

Course Materials (Included):

A 400-page course handbook is provided to each member of the class. The handbook includes copies of course slides and a list of useful online resources.

What You Will Learn?

At the completion of the course, participants should be able to understand:

Understand Agile Development

  • Foundational Agile concepts

  • Scrum basics

  • Common XP Practices

  • Problems and misconceptions of Agile

  • Misidentifications of Agile that impact test teams and solutions


Test in Agile

  • Important QA, test ideas, and practices that need to be remembered on Agile projects

  • New test practices and strategies for testing on Agile projects

  • Traditional test team responsibilities in Agile projects

  • How to cope with a significant increase in delivered code

Test Strategy for Agile

  • Continuous Integration

  • Building a new test strategy from old practices

  • Significant changes to test artifacts, specifically to test cases and test plans

  • New project management tools specifically for Agile projects

  • Test and project measurement on Agile projects

  • A new level of communication as the foundation of Agile development

  • Automation strategies in an Agile world

  • New complexities and solutions for Agile offshore testing

Course Outline

Chapter 1 - Agile: What is it?

  • How did we get here?

  • What are the common practices of Agile?

  • Example Scrum and XP practices directly related to testing

  • Test-driven development/unit testing

  • Continuous Integration

  • Acceptance testing in XP

  • Ideas about the definition of ”done”

  • Role of the “team” and Test/Quality Engineers

  • Problems and misconceptions of Agile

Chapter 2 - What This Can Mean for Testing

  • How does Agile impact testing?

  • Important Agile and quality concepts we need in Agile testing

  • Limitations of unit testing and acceptance testing

  • Test methods and techniques for Agile

    • Exploratory testing skills

    • The tasks traditional test teams did and who does them now

    • Better estimation skills

  • Skills for Agile Test Engineers

Chapter 3 - Test Artifacts in Agile

  • Does Agile mean we stop documenting?

  • User stories and test cases

  • Importance of the conversation with user stories

Chapter 4 - Tools

  • New classes of tools

Chapter 5 - Test Automation in Agile: It’s Absolutely Essential… and Different.

  • Importance of large-scale automated regression

  • Test design and framework implementation for rapid projects

  • Action-Based Testing and keyword-driven testing

Chapter 6 - Agile Offshore

  • Agile projects with outsourced and/or offshore teams

  • Some of the old, obvious problems exacerbated

  • Solutions

Chapter 7 - Agile Testing Roundtable

  • Common testing problems in Agile

  • Some politics to watch out for in Agile projects

  • ScrumButs and Agile Falls warnings!

  • Using the sprint retrospective for process improvement


  • Completion of Testing Computer Software,

  • 6 months of experience in testing, and

  • One year of experience in software development management or equivalent is suggested.

LogiGear’s collection of whitepapers aim to exhibit our decades of Software Testing expertise; from Test Automation pitfalls to test design best practices, you can download them for free today, and see how you can improve your Software Testing processes and outcomes.

Ready to transform your testing process?

Developed from decades of practical experience and academic research, LogiGear training empowers your team to meet the challenges of emerging technologies, evolving testing techniques, and a changing economy with comprehensive Software Testing curriculum. Get in contact with our team of experts to see how LogiGear can bring this same level of training and testing expertise to your organization.

Contact Us