Cross Team Testinga way to tackle bias

Johan ÅttingSectra Medical Systems

DevLin 14 March 2013

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

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

EAST: Östergötlands Association for Software Testers

Currently: Chief Quality Officer at Sectra Medical Systems

Agenda1. Background & Context2. Benefits (testers in dev teams)3. Challenges (testers in dev teams)4. Cross Team Testing5. Summary

Please note:

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

Our current practice / solution for us in our context

CONTEXT

13%

87%iRadiology IT - RIS/PACS

iOrthopedic Imaging

iRheumathology

Release testDevelopment...

...

......

12 Agile development teams

2 Testers & 4 Programmers per team

Benefitswith having testers in the development teams

Early involvement

Easier to make a difference

Bug prevention

Less admin

Better quality

No wall between test & development

Challengeswith having testers in the development teams

Biased (testing your own baby)

Less curious

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

Eye opener

We need to get fresh, unbiased, independent eyes on whats beeing

developed

• Freelance tester

• Separate test team

• Testers from other teams

• Other sources / persons

• Or a combination...

How?

• Ad hoc

• On demand

• After sprint demo

• Or...

• Beginning of next sprint

When?

Gather all testers (and anyone else that like to participate) to test each others

test objects after every sprint

Cross Team Testing

Sprint Sprint Sprint Sprint

Cro

ss T

eam

Tes

tin

g

Cro

ss T

eam

Tes

tin

g

Cro

ss T

eam

Tes

tin

g

Sprint Sprint Sprint SprintSprint Sprint Sprint SprintSprint Sprint Sprint Sprint

1 2 3 4 5 6 7 8 9 10

Two week sprintSp

rin

t P

lan

nin

g

Spri

nt

De

mo

(2 h

ou

rs)

Pla

nn

ing

(1 d

ay)

Test

ing

(30

min

) R

etr

o

Cross Team Testing

Planning (2 hours)1. High level presentation of test objects

2. Planning sessions in smaller groups

2. Planning session in small groupsa. Detailed presentation of the test object

b. Brainstorm test ideas, based on aspects

requested by the Test Owner, such as:

• Coverage criteria

• Quality characteristics (security, stability, …)

• Risks (business, technical, patient)

• Test techniques, test tools, test data

• ...or any other basis or source for test ideas

c. Create test charters (approximately 3-9)

2. Planning session in small groupsa. Detailed presentation of the test object

b. Brainstorm test ideas

c. Create test charters (approximately 3-9)• Title - Briefly identifies and describes the test idea

and/or mission in one or two sentences

• Test Area - Details any particular focus area of the test object where the Test Owner would like the testers to spend most of their session time

• Guidelines Quality characteristics (safety, security, performance, reliability, capability, usability…). Oracles (requirements, standards, design consistency…) Resources (tools, data, test technique, configuration…)

Testing (1 day)• Exploratory group testing sessions (*3)

• Debrief to the Test Owner

• Bug reporting

Time Slot Activity

9:20 Test Session #1 70min

10:30 Debreifing Session #1 15min

10:45 FIKA

11:00 Test Session #2 75min

12:15 Debreifing Session #2 15min

12:30 LUNCH

13:30 Test Session #3 75min

14:45 Debreifing Session #3 15min

15:00 -> Bug Reporting / Optional more testing

Retrospective (30 min)

Challengeswith Cross Team Testing

Finding timeMissing discussions in your team

Benefitswith Cross Team Testing

Finding bugs

Collaboration, interaction & learning

Trying new test ideas/tools/...

Fun

Test planning workshop

Takeaways

• Everyone is biased

• There is a need for independent eyes

• Cross Team Testing is one solution

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