Cross Team Testing  a way to tackle bias    Johan Åtting  Sectra Medical Systems  DevLin 14 March 2013
Twitter: @JohanAttingLinkedin: Johan ÅttingE-mail: johan.atting@sectra.com
18 years in the software businessDeveloper, Tester,                      Transport,Project Manager,                       ...
Agenda1.   Background & Context2.   Benefits (testers in dev teams)3.   Challenges (testers in dev teams)4.   Cross Team T...
Please note:Cross Team TestingNot a ”best practice”Not a ”universal solution”Our current practice / solutionfor us in our ...
CONTEXT
i Radiology IT - RIS/PACS                            87%i Orthopedic Imagingi Rheumathology                            13%
Development    Release test         ...         ...          .          .          .         ...
12 Agile development teams2 Testers & 4 Programmers per team
Benefits    with having testers in the development teamsEarly involvement              Less adminBug prevention           ...
Challenges     with having testers in the development teamsBiased (testing your own baby)Less curiousWalls between the tea...
Eye opener
We need to get fresh, unbiased,independent eyes on whats beeing           developed
•   Freelance tester                               How?•   Separate test team•   Testers from other teams•   Other sources...
•   Ad hoc                             When?•   On demand•   After sprint demo•   Or...•   Beginning of next sprint
Gather all testers (and anyone else that like to participate) to test each others      test objects after every sprint    ...
Sprint Sprint     Sprint             Sprint                Sprint                                    Sprint               ...
1  Sprint Planning                     2                     3(2 hours) Planning                          Two week sprint ...
Planning (2 hours)1. High level presentation of test objects2. Planning sessions in smaller groups
2. Planning session in small groups a.    Detailed presentation of the test object b.    Brainstorm test ideas, based on a...
2. Planning session in small groups a.    Detailed presentation of the test object b.    Brainstorm test ideas c.    Creat...
Testing (1 day)• Exploratory group testing sessions (*3)• Debrief to the Test Owner• Bug reporting
Time Slot   Activity9:20        Test Session #1                  70min10:30       Debreifing Session #1            15min10...
Retrospective (30 min)
Challenges           with Cross Team Testing                             MissingFinding time                 discussions i...
Benefits               with Cross Team TestingFinding bugs                      Trying new test                           ...
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
Cross Team Testing presentation at DevLin2013
Upcoming SlideShare
Loading in …5
×

Cross Team Testing presentation at DevLin2013

907 views

Published on

Cross Team Testing is a way to tackle bias. Having testers in the development teams have many benefits but also new challenges. One of these challenges are that the testers get biased. Cross Team Testing is a structured way to tackle this bias. This is my presentation on this subject from DevLin March 14 2013.

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
907
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Cross Team Testing presentation at DevLin2013

  1. 1. Cross Team Testing a way to tackle bias Johan Åtting Sectra Medical Systems DevLin 14 March 2013
  2. 2. Twitter: @JohanAttingLinkedin: Johan ÅttingE-mail: johan.atting@sectra.com
  3. 3. 18 years in the software businessDeveloper, Tester, Transport,Project Manager, Bank&Finance,Test Manager, Telecom andSupport Manager, MedTech.Operations Manager,Quality Manager,Line Manager...EAST: Östergötlands Association for Software TestersCurrently: Chief Quality Officer at Sectra Medical Systems
  4. 4. Agenda1. Background & Context2. Benefits (testers in dev teams)3. Challenges (testers in dev teams)4. Cross Team Testing5. Summary
  5. 5. Please note:Cross Team TestingNot a ”best practice”Not a ”universal solution”Our current practice / solutionfor us in our context
  6. 6. CONTEXT
  7. 7. i Radiology IT - RIS/PACS 87%i Orthopedic Imagingi Rheumathology 13%
  8. 8. Development Release test ... ... . . . ...
  9. 9. 12 Agile development teams2 Testers & 4 Programmers per team
  10. 10. Benefits with having testers in the development teamsEarly involvement Less adminBug prevention Better quality Easier to make a differenceNo wall between test & development
  11. 11. Challenges with having testers in the development teamsBiased (testing your own baby)Less curiousWalls between the teams(i.e. between the testers)
  12. 12. Eye opener
  13. 13. We need to get fresh, unbiased,independent eyes on whats beeing developed
  14. 14. • Freelance tester How?• Separate test team• Testers from other teams• Other sources / persons• Or a combination...
  15. 15. • Ad hoc When?• On demand• After sprint demo• Or...• Beginning of next sprint
  16. 16. Gather all testers (and anyone else that like to participate) to test each others test objects after every sprint Cross Team Testing
  17. 17. 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
  18. 18. 1 Sprint Planning 2 3(2 hours) Planning Two week sprint 4 (1 day) Testing 5 (30 min) Retro Cross Team Testing 6 7 8 9 10 Sprint Demo
  19. 19. Planning (2 hours)1. High level presentation of test objects2. Planning sessions in smaller groups
  20. 20. 2. Planning session in small groups a. 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)
  21. 21. 2. Planning session in small groups a. 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…)
  22. 22. Testing (1 day)• Exploratory group testing sessions (*3)• Debrief to the Test Owner• Bug reporting
  23. 23. Time Slot Activity9:20 Test Session #1 70min10:30 Debreifing Session #1 15min10:45 FIKA11:00 Test Session #2 75min12:15 Debreifing Session #2 15min12:30 LUNCH13:30 Test Session #3 75min14:45 Debreifing Session #3 15min15:00 -> Bug Reporting / Optional more testing
  24. 24. Retrospective (30 min)
  25. 25. Challenges with Cross Team Testing MissingFinding time discussions in your team
  26. 26. Benefits with Cross Team TestingFinding bugs Trying new test ideas/tools/...Collaboration,interaction &learning Fun Test planning workshop
  27. 27. Takeaways• Everyone is biased• There is a need for independent eyes• Cross Team Testing is one solution
  28. 28. Twitter: @JohanAttingLinkedin: Johan ÅttingE-mail: johan.atting@sectra.com

×