Traditional testing approaches involve post-development testing phases where quality is expected to be boosted after code is complete, but this illusion of control can lead to delays if requirements are not fully delivered. Agile testing is iterative and incremental, with testers testing each coding increment as soon as it is finished so that programmers never get ahead of testers and a story is not done until tested. True agile teams focus on repeatable quality and efficiency rather than just delivering specified requirements by a release date.

1. AGILE TESTING
Artem Bykovets
(ScrumMaster, IT/QA and Agile coach, founder at StartIT)

4. IN RESULT
• Post-development testing phases were expected to boost quality after code was
complete. We had the illusion of control
• Traditional teams are focused on making sure all the specified requirements are
delivered in the final product. If everything isn’t ready by the original target release
date, the release is usually postponed.
• Sometimes testers must seat and wait for some work to do

6. TRADITIONAL VS. AGILE TESTING

7. AGILE TESTING
• While some teams do seem to use the “Agile” buzzword to justify simply doing whatever
they want, true agile teams are all about repeatable quality as well as efficiency
• Agile is iterative and incremental. This means that the testers test each increment of
coding as soon as it is finished
• Programmers never get ahead of the testers, because a story is not “done” until it
has been tested

9. THANK YOU! QUESTIONS? J

10. CONTACTS:
ua.linkedin.com/in/abykovets
Skype: arthar4eg
mail: a.bykovets@start-it.com.ua
www.start-it.com.ua
https://www.facebook.com/QASTARTIT
Office: 063 742 50 52