1. Cross Team Testing
Johan Åtting
@JohanAtting
johan.atting@sectra.com
Oredev 9 Nov 2012
2. 18 years in the software business
Developer, Tester, Projec Transport, Bank&
t Manager, Finance, Telecom
Test Manager, and MedTech.
Support
Manager, Operations
Manager, Quality
Manager,
Line Manager...
Currently: Chief Quality Officer at Sectra Medical Systems
3. WARNING
Cross Team Testing
Not a ”best practice”
Not a ”universal solution”
Our current practice / solution
for us in our context
5. Development + Test Systemtest
...
...
.
.
.
...
(Example of a release project)
6. Benefits
with having testers in the scrum teams
Early involvement Less admin
Bug prevention Better quality
Easier to make a difference
No wall between test & development
7. Challenges
with having testers in the scrum teams
Biased (testing your own baby)
Less curious
Walls between the teams
(i.e. between the testers)
9. Cross Team Testing
Testing activity with testers from all teams
after each sprint in order to:
• get new eyes on whats been developed
• interact, discuss, learn
10. Sprint
Sprint Sprint
Sprint Sprint
Sprint Sprint
Sprint
Sprint
Sprint Sprint
Sprint Sprint
Sprint Sprint
Sprint
Cross Team Testing
Cross Team Testing
Cross Team Testing
Benefits:Earlier involvementBug preventionDirect feedbackLess administrationEasier to make a bigger differenceFunThe wall between Developers and Testers are gone!!!
Challenges:There are new walls... Now between the teams (or fences)Less interaction with other testersSVT testing and system testing...Biased... You know the design and how its intended to work. Difficult to play a novice user, not really objective (even if you try). Home blindness...You might loos some of your curiosity after a few sprints on the same feature.Stockholm Syndrome: (August 23 to August 28, 1973)in which hostages express empathy and have positive feelings towards their captors, sometimes to the point of defending them.
