Balancing and Growing Agile Testing with High Productive Distributed Teams

224 views

Published on

Presentation from Agile Testing Days 2012, Potsdam, Germany
Mads Troels Hansen & Oleksiy Shepetko

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
224
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Balancing and Growing Agile Testing with High Productive Distributed Teams

  1. 1. Balancing and growing agile testing with high productive distributed teams Agile Testing Days 2012 Oleksiy Shepetko & Mads Troels Hansen
  2. 2. ScanJour
  3. 3. Our Global Agile Testing Supported by 5 pillars
  4. 4. Enterprise Agile Transformation in ScanJour"React fast on opportunities and needs from customers with real solutions that create value"
  5. 5. Organisation Journey Old days
  6. 6. Organisation Journey Last couple of years
  7. 7. Organisation Journey Summer 2012
  8. 8. Towards the Customer Oriented Enterprise
  9. 9. Our Global Agile Testing 5 Problematic Areassymptoms (!) our cures (?)
  10. 10. 1: "Testing Bottleneck"
  11. 11. 1: SymptomsGrowing test backlog
  12. 12. 1: SymptomsLong stabilization phase
  13. 13. 1: SymptomsTrading off the quality
  14. 14. Cures for "Testing Bottleneck"• Quality focus in the team• Test driven development• Test automation• Early testing• Collaboration• Definition of Done
  15. 15. 2: Testing Police
  16. 16. 2: SymptomsReleases are often blocked (delayed) by testers
  17. 17. 2: SymptomsGoals for testers and developers are not aligned
  18. 18. 2: SymptomsBad atmosphere inside the team
  19. 19. 2: Cures for "Testing Police"Focusing on quality through all the activitiesFixing bugs collaboratively over registering &ranking themCollecting customer’s feedbackand product usage stats
  20. 20. 3: Remote Testing
  21. 21. 3: SymptomsTesters and Developers are in different locations ...or even... in different teams
  22. 22. 3: Symptoms Competition between disciplines:up to additional activity to "trip-up" another discipline
  23. 23. 3: SymptomsLimited understanding between disciplines
  24. 24. 3: CuresCross-functional self-contained teamsDefinition of DoneCommunity of practicesSelf-managed teams withcoaching style technicalleadership
  25. 25. 4: 1-to-1 Automation
  26. 26. 4: SymptomsTests are “red” most of the time
  27. 27. 4: SymptomsRequired maintenance is increasing
  28. 28. 4: SymptomsResults of autotests are ignored
  29. 29. 4: Cures for 1-to-1 AutomationBalance test automation & manual testingCreate separate test cases for automationUse test automation effectivelyCreate stable infrastructure
  30. 30. 4: Our Timeline
  31. 31. 5: Too Many Versions to Support
  32. 32. 5: Symptoms Need in support for very old versions:...many customers are still using them...
  33. 33. 5: Symptoms Low innovation rate:hotfixes and service packs instead of new feature releases
  34. 34. 5: Symptoms Low customer adoption:no real reasons for customers to switch to the newest version
  35. 35. 5: Symptoms Complicated upgrades: upgrade procedure istoo risky or too expensive
  36. 36. 5: CuresSolid and simple upgrade strategySupport includes upgradesContinuous integration and deliveryPotentially releasableproducts every sprint
  37. 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. DistributedOleksiy Shepetko Mads Troels Hansen @ashepetko @MadsTH
  38. 38. Please evaluate our presentationby using the evaluation booklets which you can find in your conference bag. Thank you!

×