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 Areas

symptoms (!) our cures (?)

1: "Testing Bottleneck"

1: Symptoms

Growing test backlog

1: Symptoms

Long stabilization phase

1: Symptoms

Trading 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: Symptoms

Releases are often blocked (delayed) by testers

2: Symptoms

Goals for testers and developers are not aligned

2: Symptoms

Bad atmosphere inside the team

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

3: Remote Testing

3: Symptoms

Testers 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: Symptoms

Limited understanding between disciplines

3: Cures

Cross-functional self-contained teams

Definition of Done

Community of practices

Self-managed teams with

coaching style technical

leadership

4: 1-to-1 Automation

4: Symptoms

Tests are “red” most of the time

4: Symptoms

Required maintenance is increasing

4: Symptoms

Results of autotests are ignored

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

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 is

too risky or too expensive

5: Cures

Solid and simple upgrade strategy

Support includes upgrades

Continuous integration and delivery

Potentially releasable products every sprint

Our Global Agile Testing

The 5 pillars

The 5 Problematic Areas

Balancing and growing our agile testing

Oleksiy Shepetko

Under testing vs. Over testing

Test automation vs. Manual testing

Customer adoption vs. R&D product focus

Local vs. Distributed

@ashepetko

Mads Troels Hansen

@MadsTH

Please evaluate our presentation

by using the evaluation booklets

which you can find in your

conference bag.

Thank you!