squad 2013: team collaboration for testing

24
Lisa Crispin Copyright 2013 Co-author of Agile Testing: A Practical Guide for Testers and Agile Teams, Addison-Wesley 2009 (and now working on More Agile Testing) Team Collaboration for Testing SQuAD Conference 2013 Denver, CO

Upload: lisacrispin

Post on 10-May-2015

411 views

Category:

Technology


2 download

TRANSCRIPT

Page 1: SQuAD 2013: Team Collaboration for Testing

Lisa CrispinCopyright 2013

Co-author of Agile Testing: A Practical Guide for Testers and Agile Teams, Addison-Wesley 2009 (and now working on More Agile Testing)

Team Collaboration for TestingSQuAD Conference 2013

Denver, CO

Page 2: SQuAD 2013: Team Collaboration for Testing

About me:I like collaboration!

Page 3: SQuAD 2013: Team Collaboration for Testing

About you:Do you work on a cross-functional team?

Do you have access to

stakeholders?

Page 4: SQuAD 2013: Team Collaboration for Testing

Develop the right thing

Develop the thing right

Why Collaborate?

Page 5: SQuAD 2013: Team Collaboration for Testing

Collaboration Game: Iteration 1, 5 minutes Form teams of four: coder, tester, customer, and

observer Coder faces away from customer and tester Customer tells the coder what to draw, all at one time. Coder draws the shapes based on what the customer

explained. No talking during ‘coding’!

Tester “tests” the drawing, writes down “bugs” Coder fixes the “bugs” How long did it take? Is the customer happy?

Page 6: SQuAD 2013: Team Collaboration for Testing

Collaboration Game: Iteration 2, 5 minutes Collaborate! Customer and tester tell coder what to draw, and watch

the coder draw, answer questions, point out ‘defects’ for programmer to fix immediately (Don’t show the coder the drawing, that makes it too

easy, we’re trying to simulate real coding) How long did it take? Is the customer happy? How did that feel compared to Iteration 1?

Thanks to the members of the agile-games group and Kane Mar for ideas & pictures for this game

Page 7: SQuAD 2013: Team Collaboration for Testing

Collaboration practices

ATDD /SBE

Impact Mapping

Story MappingListen to

customers√Pair

Page 8: SQuAD 2013: Team Collaboration for Testing

ATDD (Acceptance Test Driven Development)

UserStory

ExpandTests

High levelAT

Auto-mate tests

Code&

Execute tests

Explore

Exploratory Testing

AcceptStory

Fix defects

Explore examples

Page 9: SQuAD 2013: Team Collaboration for Testing

• Examples provide common language• Shared vision• Coding and testing concurrently• Involves whole team• Shared definition of DONEBonus: prevents defects!

How ATDD helps collaboration

Recommended books:Specification by Example, Gojko AdzicATDD by Example, Markus Gaertner

Page 10: SQuAD 2013: Team Collaboration for Testing

• Why are we doing this?• Who can help? Hinder? Who is impacted?• How can they help or hinder? Impacts• What can we do to support impacts?

Deliverables

Impact Mapping

Page 11: SQuAD 2013: Team Collaboration for Testing

Example Impact Map

Based on example at http://impactmapping.org, Gojko AdzicRecommended book: Impact Mapping

Page 12: SQuAD 2013: Team Collaboration for Testing

Using impact mapping to problem-solve

Page 13: SQuAD 2013: Team Collaboration for Testing

Copyright 2012Lisa Crispin, Janet Gregory.

Story Mapping

Activities by time

Child

Sto

ries

From Janet Gregory & Matt Barcomb

Jeff Patton: http://www.agileproductdesign.com/blog/the_new_backlog.html

Page 14: SQuAD 2013: Team Collaboration for Testing

From Janet Gregory & Matt Barcomb

Page 15: SQuAD 2013: Team Collaboration for Testing

Listen to your customers!

Page 16: SQuAD 2013: Team Collaboration for Testing

Collaboration helps simplify, deliver what customers want most

Page 17: SQuAD 2013: Team Collaboration for Testing
Page 18: SQuAD 2013: Team Collaboration for Testing

18

Pair

Page 19: SQuAD 2013: Team Collaboration for Testing

19

Supportive culture, infrastructure

Page 20: SQuAD 2013: Team Collaboration for Testing

20

Multiple roles, multiple activities

Tester-Designer

Tester-Support

Tester-Tester

Tester-Coder

Analyst, DBA, Sys Admin, Customer…

Tester-Marketer

Page 21: SQuAD 2013: Team Collaboration for Testing

Become a “generalizing specialist”

"An individual with a deep level of knowledge in at least one domain and a collaborative understanding of at least one other."

Basics

Advanced

Meta

Page 22: SQuAD 2013: Team Collaboration for Testing

Multi- discipline skillsExpert / Discipline skills

Recommended: http://thesocialtester.co.uk/t-shaped-tester-square-shaped-team/

Page 23: SQuAD 2013: Team Collaboration for Testing

Collaboration practices

ATDD /SBE

Impact Mapping

Story MappingListen to

customers√Pair

Page 24: SQuAD 2013: Team Collaboration for Testing

Your stories?