This document summarizes a presentation given by Oleksiy Shepetko and Mads Troels Hansen on growing agile testing with distributed teams. It outlines ScanJour's journey towards becoming a more customer-oriented enterprise through agile transformation supported by 5 pillars. It then discusses 5 problematic areas for global agile testing, including testing bottlenecks, remote testing challenges, test automation issues, and difficulties supporting multiple product versions. Potential cures are proposed for each problem area, such as focusing on quality, defining a done criteria, using cross-functional teams, and implementing a solid upgrade strategy. The presentation aims to find a balance between under and over testing, different testing approaches, and local vs distributed work.

1. Balancing and growing agile testing with
high productive distributed teams
Agile Testing Days 2012
Oleksiy Shepetko & Mads Troels Hansen

2. ScanJour

3. Our Global Agile Testing
Supported by 5 pillars

4. Enterprise Agile Transformation in ScanJour
"React fast on opportunities and
needs from customers with real
solutions that create value"

5. Organisation Journey
Old days

6. Organisation Journey
Last couple of years

7. Organisation Journey
Summer 2012

8. Towards the Customer Oriented Enterprise

9. Our Global Agile Testing
5 Problematic Areas
symptoms (!) our cures (?)

10. 1: "Testing Bottleneck"

11. 1: Symptoms
Growing test backlog

12. 1: Symptoms
Long stabilization phase

13. 1: Symptoms
Trading off the quality

14. Cures for "Testing Bottleneck"
• Quality focus in the team
• Test driven development
• Test automation
• Early testing
• Collaboration
• Definition of Done

15. 2: Testing Police

16. 2: Symptoms
Releases are often blocked (delayed) by testers

17. 2: Symptoms
Goals for testers and developers are not aligned

18. 2: Symptoms
Bad atmosphere inside the team

19. 2: Cures for "Testing Police"
Focusing on quality through all the activities
Fixing bugs collaboratively over registering &
ranking them
Collecting customer’s feedback
and product usage stats

20. 3: Remote Testing

21. 3: Symptoms
Testers and Developers are
in different locations
...or even...
in different teams

22. 3: Symptoms
Competition between disciplines:
up to additional activity to "trip-up"
another discipline

23. 3: Symptoms
Limited understanding between disciplines

24. 3: Cures
Cross-functional self-contained teams
Definition of Done
Community of practices
Self-managed teams with
coaching style technical
leadership

25. 4: 1-to-1 Automation

26. 4: Symptoms
Tests are “red” most of the time

27. 4: Symptoms
Required maintenance is increasing

28. 4: Symptoms
Results of autotests are ignored

29. 4: Cures for 1-to-1 Automation
Balance test automation & manual testing
Create separate test cases for automation
Use test automation effectively
Create stable infrastructure

30. 4: Our Timeline

31. 5: Too Many Versions to Support

32. 5: Symptoms
Need in support for very old versions:
...many customers are still using them...

33. 5: Symptoms
Low innovation rate:
hotfixes and service packs
instead of
new feature releases

34. 5: Symptoms
Low customer adoption:
no real reasons for customers to switch to
the newest version

35. 5: Symptoms
Complicated upgrades:
upgrade procedure is
too risky or too expensive

36. 5: Cures
Solid and simple upgrade strategy
Support includes upgrades
Continuous integration and delivery
Potentially releasable
products every sprint

37. Balancing and growing our agile testing
Under testing vs. Over testing
Test automation vs. Manual testing
Customer adoption vs. R&D product focus
Local vs. Distributed
Oleksiy Shepetko Mads Troels Hansen
@ashepetko @MadsTH

38. Please evaluate our presentation
by using the evaluation booklets
which you can find in your
conference bag.
Thank you!