cross team testing oredev nov 2012 - johan åtting

17
Cross Team Testing Johan Åtting @JohanAtting [email protected] Oredev 9 Nov 2012

Upload: johan-atting

Post on 12-Jun-2015

420 views

Category:

Documents


5 download

TRANSCRIPT

Page 1: Cross team testing   oredev nov 2012 - johan åtting

Cross Team Testing

Johan Åtting@JohanAtting

[email protected]

Oredev 9 Nov 2012

Page 2: Cross team testing   oredev nov 2012 - johan åtting

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

Page 3: Cross team testing   oredev nov 2012 - johan åtting

WARNING

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

Our current practice / solution for us in our context

Page 4: Cross team testing   oredev nov 2012 - johan åtting

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

Page 5: Cross team testing   oredev nov 2012 - johan åtting

SystemtestDevelopment + Test...

...

......

(Example of a release project)

Page 6: Cross team testing   oredev nov 2012 - johan åtting

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

Page 7: Cross team testing   oredev nov 2012 - johan åtting

Challenges with having testers in the scrum teams

Biased (testing your own baby)

Less curious

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

Page 8: Cross team testing   oredev nov 2012 - johan åtting

Trigger

Page 9: Cross team testing   oredev nov 2012 - johan åtting

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

Page 10: Cross team testing   oredev nov 2012 - johan åtting

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

Page 11: Cross team testing   oredev nov 2012 - johan åtting

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

Page 12: Cross team testing   oredev nov 2012 - johan åtting

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

Page 13: Cross team testing   oredev nov 2012 - johan åtting

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

Page 14: Cross team testing   oredev nov 2012 - johan åtting

Retrospective (30 min)

Page 15: Cross team testing   oredev nov 2012 - johan åtting

Challenges

Finding time

Missing discussions in your team

Page 16: Cross team testing   oredev nov 2012 - johan åtting

BenefitsFinding bugs

Colloboration, interaction & learning

Trying new test ideas/tools/..

Fun

Test idea workshop

Page 17: Cross team testing   oredev nov 2012 - johan åtting

Twitter: @JohanAttingLinkedin: Johan ÅttingE-mail: [email protected]