Agile Testing in Enterprise: Way to transform

1. Agile Testing in Enterprise: Way
to transform
Andrei Rebrov
Agile Coach

3. Disclaimer

4. Our waypoints

5. Table of content
• “True Story”
• What kind of problems do we usually
notice
• What kind of problems really happens
• How to change your process
• Good practices
• Next steps

6. “True story”

7. Story #1
• Prerequisites:
– 1 dev team
– 2 QA engineers
• Problems:
– long regression cycle
– unmet estimates
– low product quality
– total stress

8. Story # 2
• Prerequisites
– huge bank with its own culture
– testing performed by BA
– chaos
• Problems:
– low product quality
– slow delivery
– unstable infrastructure

9. Why does company need to change?
It’s cool We have budget
Conference talk We want to survive

10. Business need it

11. What business doesn’t like
• estimates and delivery speed
• vendor’s bureaucracy
• no ways to experiment

12. Let’s talk about IT

13. • Business wants everything and right now
• No way for growth
• Need in building high quality products
What IT doesn’t like

14. We need perfect World!

15. But to be honest, we want…
• Get right product
• In predictable time and quality
• Improve team and product

16. Time to cure

18. Root cause
• document-based collaboration
• developers don’t know about testing
practices
• chaos in infrastructure management
• work time utilization -‐> no time for
improvement

19. Let’s start from scratch

20. Untranslated Russian joke, saying
«Don’t call your laziness corporate culture»

21. What is quality

22. Maslow’s Hierarchy of Needs

23. Gojko Adzic Quality Hierarchy

24. Kanban to Focus

25. Collaboration during BA

26. Team should know what to test

27. Time to manage risks

28. Easiest way

29. Risks in QA
• Infrastructure denial
• Bus factor
• Test automation engineer who likes
snowboarding

30. Continuous Quality

32. Тестирование и DevOps

34. Culture Automation
Measurement Sharing

36. Summary

37. • Kanban to help us synchronize and collaborate
• Common work on requirements
• Smart quality metrics
• Test Automation
• Agile testing quadrant model as whole team
approach for testing
• DevOps approach to manage infrastucture
What we implemented

38. • Risk management
• Spec By Example
• TDD + Integration testing (test
automation pyramid)
• Continuous Integration
• Automation configuration
• Test automation
• Proactive monitoring
Implemented practices

39. What do we have now
• Delivery rate increased up to 5 times
• 2-3 delivery every weak
• Zero bugs in productions
• No more overtimes
• Work became enjoyable

40. Next steps
• Mentorship
• Usability testing
• Non functional testing
• Engineer in test

42. Twitter
@andrebrov
E-mail
arebrov@scrumtrek.ru
Skype
rebrov.andrey
Q&A