cross team testing oredev nov 2012 - johan åtting

Cross Team Testing

Johan Åtting@JohanAtting

johan.atting@sectra.com

Oredev 9 Nov 2012

Developer, Tester, Project Manager, Test Manager, Support Manager, Operations Manager, Quality Manager, Line Manager...

Transport, Bank&Finance, Telecom and MedTech.

18 years in the software business

Currently: Chief Quality Officer at Sectra Medical Systems

WARNING

Cross Team TestingNot a ”best practice” Not a ”universal solution”

Our current practice / solution for us in our context

12 Development teams1-2Testers and 3-4Programmers per team2 Weeks sprints

SystemtestDevelopment + Test...

...

......

(Example of a release project)

Benefitswith having testers in the scrum teams

Early involvement

Easier to make a difference

Bug prevention

Less admin

Better quality

No wall between test & development

Challenges with having testers in the scrum teams

Biased (testing your own baby)

Less curious

Walls between the teams(i.e. between the testers)

Trigger

Cross Team TestingTesting activity with testers from all teams after each sprint in order to:

• get new eyes on whats been developed• interact, discuss, learn

Sprint Sprint Sprint Sprint

Cros

s Te

am T

estin

g

Cros

s Te

am T

estin

g

Cros

s Te

am T

estin

g

Sprint Sprint Sprint SprintSprint Sprint Sprint SprintSprint Sprint Sprint Sprint

1 2 3 4 5 6 7 8 9 10

Two week sprintSp

rint P

lann

ing

Sprin

t Dem

o

(1h)

Wor

ksho

p

(1 d

ay) T

estin

g

(30

min

) Ret

ro

Cross Team Testing

Workshop (1h)• Divide into groups• Generate ideas for exploratory test sessions

Testing (1 day)• Pair testing exploratory sessions• Debrief to the ”Test Owner”• Bug reporting

Retrospective (30 min)

Challenges

Finding time

Missing discussions in your team

BenefitsFinding bugs

Colloboration, interaction & learning

Trying new test ideas/tools/..

Fun

Test idea workshop

Twitter: @JohanAttingLinkedin: Johan ÅttingE-mail: johan.atting@sectra.com