distributed agile testing: yes, you can

Post on 22-Jan-2015

121 Views

Category:

Technology

2 Downloads

Preview:

Click to see full reader

DESCRIPTION

When agile development first gained popularity, agile meant collocated teams, including testers, programmers, analysts, and customers who were expected to perform many functions. As agile methods have spread and expanded, many organizations with globally-distributed teams are facing challenges with their agile deployment. Having worked with many such teams, Janet Gregory has observed ways that testers in agile teams can be very productive while delivering a high-quality software product and working well with the rest of the team. In this interactive session, Janet shares her experiences and offers opportunities for all participants to discuss their specific issues and potential solutions. Whether your distributed team is scattered across time zones, has individuals working remotely from home, or is part of an offshore outsourced project, you’ll take away methods and tools to help develop open communication, deal with cultural differences, and share data and information across the miles.

TRANSCRIPT

TP PM Tutorial

4/30/13 1:00PM

Distributed Agile Testing:

Yes, You Can

Presented by:

Janet Gregory

DragonFire, Inc.

Brought to you by:

340 Corporate Way, Suite 300, Orange Park, FL 32073

888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com

Janet Gregory

Agile testing coach and practitioner Janet Gregory (@janetgregoryca) is the coauthor of Agile Testing: A Practical Guide for Testers and Agile Teams and a contributor to 97 Things Every Programmer Should Know. Janet specializes in showing agile teams how testers can add value in areas beyond critiquing the product. For the past ten years, she has been working with teams to transition to agile development. Janet teaches agile testing courses and tutorials worldwide, contributes articles to leading publications, and enjoys sharing her experiences at conferences and user group meetings worldwide. Find more information at janetgregory.ca or visit her blog.

13/03/2013

1

Janet Gregory, DragonFire Inc.Copyright 2013

StarEast 2013

Orlando, Florida

With input from Lisa Crispin

1

Copyright 2013

DragonFire Inc.

My experience comes …

As a tester, working on co-located agile teams,

several distributed teams

Coached interviewed distributed teams world wide

Twitter: @janetgregoryca

janet@agiletester.ca

www.janetgregory.ca

2

13/03/2013

2

Copyright 2013

DragonFire Inc. 3

Copyright 2013

DragonFire Inc.

Let’s learn a bit about your experiences

- Different cities, same time zone (or 1 hr. apart)

- Time zones more than 3 hrs difference

- More than 7 hrs difference

- More than one continent

- More than 3 remote teams

- Others?

4

13/03/2013

3

Copyright 2013

DragonFire Inc.

What are your issues with distributed teams?

Don’t forget to consider testing issues…

15 - 20 minutes to capture issues

Then debrief & share

Copyright 2013

DragonFire Inc. 6

13/03/2013

4

• Cost savings

• Mergers & acquisitions

• Remote availability

• Lack of expertise

in-house

7

Copyright 2013

DragonFire Inc.

• Able to hire the ‘right’ people

◦ Independent of where they live

• Leverage time zones to your advantage

◦ Shorten feedback cycle

• More diversity

8

13/03/2013

5

Copyright 2013

DragonFire Inc.

• Extra communication efforts

• Time zone differences

• Dependencies

• Less productive

9

Copyright 2013

DragonFire Inc.

Instead of saying NO,

or being the gatekeeper

Be the information provider so

business can make the decisions

Questions… on limitations / benefits?

10

13/03/2013

6

Copyright 2013

DragonFire Inc. 11

Distributed teams means cultural issues. Many teams just don’t take it into consideration.

12

13/03/2013

7

Copyright 2013

DragonFire Inc.

Norms & valuesLanguage

Infrastructure challenges

History, habitsInteractions

13

• Accents

• English as a second language

• Attitudes – assertive vs. reserved / humble

• Saving face

14

13/03/2013

8

Infrastructure Challenges

What we

think of as

“normal”,

may not be

for everyone

15

Copyright 2013

DragonFire Inc.

It’s relatively simple for a co-located team to

adapt to agile, make the values’ their own,

and follow the principles.

16

13/03/2013

9

• Lack of trust

• Lack of face time

• Splitting work between teams

• Collaboration / Communication

17

Copyright 2013

DragonFire Inc. 18

13/03/2013

10

Copyright 2013

DragonFire Inc.

• Give the benefit of the

doubt to team members

• Think constantly of

distributed teams

members

• Extend help to others

19

Copyright 2013

DragonFire Inc.

Get entire team in one place

◦ At the start of the project

◦ Regular intervals (if possible)

20

• At a minimum,

individuals spend

time in other

locations

13/03/2013

11

Copyright 2013

DragonFire Inc.

• Divide up work

• Use time zones to your advantage

• What are some ways to do this?

21

Copyright 2013

DragonFire Inc.

Instead of saying NO,

or being the gatekeeper

Be the information provider so

business can make the decisions

Questions… cultural & team challenges?

22

13/03/2013

12

Copyright 2013

DragonFire Inc. 23

Copyright 2013

DragonFire Inc.

• Collaboration means ...

◦Working together to find solutions, etc.

• Communication means ... sharing

◦ Ideas, information, decisions, solutions, etc.

◦ Understand the media

◦ Know the audience

24

13/03/2013

13

Copyright 2013

DragonFire Inc.

• Set up communication channels so all team

members have access to

◦ decisions made

◦ planning sessions

◦ meeting notes

• Lowest common denominator for

communication

25

Copyright 2013

DragonFire Inc.

• Common orientation

• Off –shore teams

• Acquired teams

• New remote team members

26

13/03/2013

14

Copyright 2013

DragonFire Inc. 27

Let’s talk about tools & practices for

communication & collaboration 28

13/03/2013

15

Copyright 2013

DragonFire Inc.

• Email

◦ Broadcast, individual, follow-up on

conversations

• Photos – task boards, smart boards

• Videos

Remember .....

• Emails do not show emotions and

can be misinterpreted

29

Copyright 2013

DragonFire Inc.

• Telephone

• Chat rooms

• Wiki

• Collaborative automation tools

• Mind-mapping tools

• Remote pairing: VPN, Skype, instant messaging,

desktop sharing

30

13/03/2013

16

Copyright 2013

DragonFire Inc.

• Use video whenever possible

◦ Skype, Google phone, teleconferencing

• Put faces on stories and tasks

◦ Physical task boards

◦ On-line systems

◦ Use avatars

31

• Dedicated laptop on

wheels

• Good headsets

• Good microphones

32

13/03/2013

17

Anybody have any other

suggestions / stories to share

about tools they’ve used

successfully?

33

Copyright 2013

DragonFire Inc.

Instead of saying NO,

or being the gatekeeper

Be the information provider so

business can make the decisions

Questions… on Tools?

34

13/03/2013

18

Copyright 2013

DragonFire Inc. 35

• Tests provide feedback

• Tests show desired behaviour

• Developers think about testability

• Testers think about the big picture

• Multiple skill sets mean better solution

36

13/03/2013

19

• Keep the feedback cycle short

• Remove dependencies early

37

Note:

Feature teams

are preferable

with all team

members

co-located

38Picture by Augusta Evangelisti, based on diagram from Elisabeth Hendrickson

13/03/2013

20

Copyright 2013

DragonFire Inc.

How is testing affected when you have feature

teams vs. component teams?

39

Let’s share

Generate some ideas about how to split work

between teams so that collaboration can happen.

The story: As Amazon marketing manager, I want

to offer free delivery options, so that customers

will buy multiple items at once.

Acceptance:

Orders of 5 or more books get free delivery

40

Discuss at your tables, and come up with various

examples that might make the story more clear.

13/03/2013

21

The story: As Amazon marketing manager, I want

to offer free delivery options, so that customers

will buy multiple items at once.

Acceptance:

Orders of 5 or more books get free delivery

41

Now,

exchange the examples with another table.

• Do you think that this might work with a remote

team?

• Would it help clarify what was wanted?

• Power of 3

• Pairing

• Question

• Draw pictures

• Repeat verbal

conversations in

writing

42

13/03/2013

22

Copyright 2013

DragonFire Inc.

• Continuous integration

• Integrate testing and coding

• Use common tools

◦ Version control

◦ Test frameworks

◦ Defect tracking

43

Consider

operations /

maintenance

teams for

support of tests,

code

• Share information

• Share awareness of

dependencies

• Keep everyone “in

the loop”

• Same vision

• Same goal

44

13/03/2013

23

Copyright 2013

DragonFire Inc.

Instead of saying NO,

or being the gatekeeper

Be the information provider so

business can make the decisions

Questions… on Key Practices?

45

Copyright 2013

DragonFire Inc. 46

13/03/2013

24

• The right support

◦ For self-organizing teams

◦ Extra positions for liaison

• Foster a learning culture

◦ Tolerate mistakes

◦ Personal safety

• Give time to

experiment, to try

47

Copyright 2013

DragonFire Inc.

• Schedules

◦ Overlapping times

◦ Meetings

◦ Share the pain

• Use retrospectives

◦ Identify problem areas

◦ Experiment with solutions

48

13/03/2013

25

Copyright 2013

DragonFire Inc.

Copyright 2013

DragonFire Inc.

• Pick one of the challenges from the first

exercise

• What experiments might you try?

• User flip charts, markers, sticky notes...

• Prepare to share top experiment with the

group

13/03/2013

26

Copyright 2013

DragonFire Inc.

Copyright 2013

DragonFire Inc.

Instead of saying NO,

or being the gatekeeper

Be the information provider so

business can make the decisions

Questions… on adapting?

52

13/03/2013

27

Copyright 2013

DragonFire Inc. 53

Copyright 2013

DragonFire Inc.

• Whole team

• Small chunks of work

• Use your diverse skills

• Respect culture: yours and others

• Give teams time to experiment, learn

• Maintain discipline

• Avoid silos – geographical or functional

54

13/03/2013

28

Think of new ways to collaborate and communicate

Remote team

member

55

Copyright 2013

DragonFire Inc.

Collaborate to innovate

or

Innovate to collaborate

Use retrospectives to improve!!

56

13/03/2013

29

Copyright 2013

DragonFire Inc.

Agile Testing: A Practical Guide for

Testers and Agile Teams

By Lisa Crispin and Janet Gregory

www.agiletester.ca

Contact info

www.janetgregory.ca

http://janetgregory.blogspot.com/

Email: janet@agiletester.ca

Twitter: janetgregoryca

57

Copyright 2013

DragonFire Inc.

• Practices for Scaling Lean & Agile Development: Large,

Multisite and Offshore Product Development with Large-Scale

Scrum, Craig Larman and Bas Vodde, Addison-Wesley, 2010

• Agile Software Development in the Large: Diving into the

Deep, Jutta Eckstein, Dorset House, 2004

• Fearless Change: Patterns for introducing new ideas, Linda

Rising and Mary Lynn Manns

• Agile-testing@yahoogroups.com

• Pictures taken on safari in Kenya and Tanzania with Nature

Encounters Tours, British Columbia

58

13/03/2013

30

Copyright 2013

DragonFire Inc.

• www.lisacrispin.com

• Rothman Consulting Group, Inc. Vol 9, #5: Building Trust in

any Team

• Version One - State of Agile Development Survey:

http://www.versionone.com/pdf/7th-Annual-State-of-Agile-

Development-Survey.pdf

• http://leadingsoftwaretestinginanagileworld.blogspot.co.uk/2

011/03/distributed-agile-test-teams-making-it.html

59

top related