Уже много было сказано о тестировании в Agile, но в своем докладе я хочу углубиться в детали и поговорить о: - месте QA в классических моделях разработки: а был ли это действительно процесс обеспечения качества? - Agile манифесте и его ценности для QA команды - традиционном vs Agile подходе к разработке: риски, получение value, прозрачность процессов и нагрузка на команды - тестовой документации в Agile: нужна ли она? - том, как с пользой не писать Test Plan и что делать с тест кейсами и чек-листами

1. Киев 2016
Первый в Украине фестиваль тестирования
Как выживать
тестировщику в Agile
среде
Artem Bykovets
(CEO, Coach at StartIT, Agile Coach at Levi9)

2. Киев 2016
Few words about myself
Software testers: how to survive in Agile Environment
• CEO and coach/mentor at "StartIT”
• CSM, CSPO, CSP by Scrum Alliance
• Certified Kanban System Design (KMP I) by LKU.
• Agile Coach at Levi9 and Agile Consultant.
• Best QA specialist of Ukraine by IT Awards 2015
• Judge and Expert at UA Web Challenge.
• “Software quality and testing” lecturer at KPI
• Happy father of Sophiia 

3. Киев 2016
Classic model:
Software testers: how to survive in Agile Environment

4. Киев 2016
In result:
Software testers: how to survive in Agile Environment
• Post-development testing phases were expected to
boost quality after code was complete. We had the
illusion of control

5. Киев 2016
In result:
Software testers: how to survive in Agile Environment
• 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.

6. Киев 2016
In result:
Software testers: how to survive in Agile Environment
• Sometimes software testers must seat and wait for
some work to do

7. Киев 2016
The evolution:
Software testers: how to survive in Agile Environment

8. Киев 2016
The evolution:
Software testers: how to survive in Agile Environment

9. Киев 2016
Agile vs traditional:
Software testers: how to survive in Agile Environment
Work Mode
Visibility
Business Value
Risks

10. Киев 2016Software testers: how to survive in Agile Environment

11. Киев 2016
What about documentation?
Software testers: how to survive in Agile Environment

12. Киев 2016
What about documentation?
Software testers: how to survive in Agile Environment

13. Киев 2016
Requirements to
documentation?
Software testers: how to survive in Agile Environment
We need to consider what and how much documentation
should we be doing.
1) Documentation should serve the needs of the team, the
project and the customer (both the end customer and the
organisation) - anything else is a waste of effort.
2) We value living documentation over archival
documentation.
Key factors are: visible, living not archival, accessible and useful.

14. Киев 2016
Working agile documentation
Software testers: how to survive in Agile Environment

15. Киев 2016
Thank you! Questions? 
Software testers: how to survive in Agile Environment

16. Киев 2016
Contacts:
Software testers: how to survive in Agile Environment
ua.linkedin.com/in/abykovets
Skype: arthar4eg
mail: a.bykovets@start-it.com.ua
www.start-it.com.ua
https://www.facebook.com/QASTARTIT
https://www.facebook.com/startit.Agile