• Like
  • Save
Balancing and growing agile testing with high productive distributed teams
Upcoming SlideShare
Loading in...5
×
 

Balancing and growing agile testing with high productive distributed teams

on

  • 680 views

Presented at Agile Testing Days 2012

Presented at Agile Testing Days 2012

Statistics

Views

Total Views
680
Views on SlideShare
580
Embed Views
100

Actions

Likes
0
Downloads
7
Comments
0

4 Embeds 100

http://blog.lean-agile.dk 93
http://www.linkedin.com 3
https://www.linkedin.com 2
https://twitter.com 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Balancing and growing agile testing with high productive distributed teams Balancing and growing agile testing with high productive distributed teams Presentation Transcript

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