When transitioning from traditional approaches to Agile development, teams need to think differently about testing/quality as well as use different practices. Testers are no longer handed the code after developers have finished working on it, rather, quality/testing is an integral activity as part of the agile cross-functional team.

In this workshop for Testers, Testing Leads, Dev Managers/Leads and Scrum Masters/Agile Coaches you will learn about Agile Testing – a set of principles and practices that will help you build quality into agile teams. Expect to learn about Whole Team Ownership of Automation, Test-First approaches such as ATDD/BDD/TDD, Establishing effective testing flow, the Test Automation Pyramid, Economic/Cost of Delay principles of establishing an effective testing strategy, and more.

The workshop includes interactive exercises and real life situations, covers the key factors for successful Agile Testing implementation and provides important insights and best practices that can be implemented in your Agile teams.

Our Agile Testing Trainers

  • Yuval Yeret SAFe SPCT, Professional Scrum Trainer (PST), Enterprise Agile/Agile Marketing Transformations Consultant, Head of AgileSparks USA, CTO

Some indications you might need to look at “Agile Testing”

  • You applied WIP (Work in Process) Limits and Testing is becoming a bottleneck. Not once or twice, but quite consistently.
  • You agreed to include test automation as part of the “Definition of Done” and you are seeing a queue building up meaning the automation is slowing the entire process down, creating significant slack for the people NOT doing automation.
  • You find a lot of defects which send you to rework technical design due to lack of mutual understanding of the functional requirements / stories, or you find yourself leaving things ugly since there is no time to do the rework – earning you some customer feedback that you are not really providing high quality deliverables.
  • You are not able to run a very granular flow – everyone claims smaller stories are not useful since the overhead to deliver them to testing and test them is so high. Let’s just keep using bigger items and deliver to testing not more than every 1-2 weeks.
  • People feel that the test automation approach you have now doesn’t cut it. The total cost of ownership / lifetime costs are very high, and even though people understand the need to have automated coverage in order to integrate often, they are very frustrated by the costs.
  • Testers are confused. Do they need to be automation specialists? Domain experts? Technical experts? Supermen? In this Agile Whole Team approach where there is flexibility and collective ownership – what is their unique value? what should they focus on?

Testimonials from previous Agile Testing participants:

  • “As usual I find ‘Agile Sparks’ guys to be real professionals, the instructor delivered a very beneficial course.”
  • “For me the course covered gaps and holes in the ‘Agile’ methodology which are related to QA role and practices in complex projects, making it more ‘down to earth’ approach for us.”
  • “The content of the course was very professional.
  • “The lecturer was very clear and gave many examples.”
  • “Fun, dynamic course, thought provoking and effective with a lot of added value and practical implementation practices.”
  • “Very informative, technical and delivered well”
  • “The dynamics of the course kept it interesting.  The course was delivered in a great, effective and enjoyable manner.” 
  • “Helped me understand well how to plan and be able to deliver higher quality using test automation. I learned also about tools that other companies are currently using.”
  • “The workshop provided skills for approaching the implementation of test automation, including how to convince my organization to move towards it.”

Interested in Agile Testing/QA?

Start typing and press Enter to search