Today, three things are undeniable facts of business—projects are becoming more agile, teams are learning to function well remotely, and the tester’s role is evolving. Mike Hrycyk believes that testers in agile teams face daunting challenges and often struggle to keep up with the pace of new feature development while performing all the needed regression testing activities. Mike offers a strategy as an alternate path: the creation of a regression testing team to augment feature teams, one that works in parallel, handling the testing regression cycle while the feature teams—developers and testers—continue to work through new development. Mike offers tips for successful feature handoff, intra-team communication, and troubleshooting hurdles that will be encountered. Although augmented regression testing is at odds with the advice of many agile “experts,” it enabled their agile development to achieve higher velocity.

1.
W16
Agile
Testing
10/4/17
15:00
Augmenting
Regression
Testing
in
Agile
Teams
Presented
by:
Mike
Hrycyk
PQA
Testing
Brought
to
you
by:
350
Corporate
Way,
Suite
400,
Orange
Park,
FL
32073
888-­‐-­‐-­‐268-­‐-­‐-­‐8770
·∙·∙
904-­‐-­‐-­‐278-­‐-­‐-­‐0524
-­‐
info@techwell.com
-­‐
http://www.starwest.techwell.com/

2.
Mike
Hrycyk
PQA
Testing
Director
of
quality
for
PQA
Testing
Mike
Hrycyk
has
been
trapped
in
the
world
of
quality
since
he
first
did
user
acceptance
testing
nineteen
years
ago.
He
has
survived
all
the
different
levels
and
a
wide
spectrum
of
technologies/environments
to
become
the
quality
dynamo
that
he
is
today.
Mike
believes
in
creating
a
culture
of
quality
throughout
software
production
and
strives
to
create
teams
that
not
only
share
this
ideal
but
also
advocate
it
to
the
rest
of
their
workmates.
Previously
he
worked
in
social
media
management,
parking,
manufacturing,
web
photo
retail,
music
delivery
kiosks,
and
at
a
railroad.
Intermittently,
Mike
blogs
about
quality
and
tweets.

3. 1
©
PQA
Tes*ng
Ltd.
Augmen*ng
Regression
Tes*ng
in
Agile
Teams
A
Tes*ng
Success
Story
©
PQA
Tes*ng
Ltd.
Mike Hrycyk
• Director
of
Quality
at
PQA
Tes*ng
• 19
years
experience
in
tes*ng
• @qaisdoes
• www.qaisdoes.com

4. 2
©
PQA
Tes*ng
Ltd.
Let’s Set a Frame of Reference
Some
pre-­‐condi*ons
• Agile
works
• It’s
preIy
well
documented
• Every
situa*on
is
different
–
by
JAY
DERAGON
this
complicates
things
©
PQA
Tes*ng
Ltd.
Complexity Complicates Things…
• It
never
hurts
to
state
the
obvious
• Mul*ple
vendors/contributor
streams
• Integra*on
tes*ng
• Extended
teams
• Mul*ple
tools/tool
sets

5. 3
©
PQA
Tes*ng
Ltd.
Building Successful Agile Teams
that Aren’t Collocated is Hard
• Not
Impossible
• But
hard
by
TAM
MACTAVISH
by
HTTPS://HAMMOCKTOWN.COM/
©
PQA
Tes*ng
Ltd.
SeCng the Stage
• Us
–
PQA
Tes*ng
and
PLATO
Tes*ng

6. 4
©
PQA
Tes*ng
Ltd.
SeCng the Stage
• Them
–
Retail
Management
So^ware
provider
(client)
by
EBAY
©
PQA
Tes*ng
Ltd.
SeCng the Stage
• Feature
Team
• Handles
Carrier
Integra*ons
• Other
Feature
Teams
• Complicated
Regression
Suite
by
F1TECHNICAL.NET

7. 5
©
PQA
Tes*ng
Ltd.
SeCng the Stage
• History
–
Failed
Experiment
• Embedded
tester
©
PQA
Tes*ng
Ltd.
The Problem
• How
does
the
client
add
remote
resources
to
solve
the
problem
of
SIT
tes*ng
regularly
overwhelming
the
feature
team?
by
RONAN
FOLLIC

8. 6
©
PQA
Tes*ng
Ltd.
Our Approach
• Determine
what
the
real
problem
is
• Don’t
get
hung
up
in
tradi*onal
agile
approaches
hIp://www.hollinden.com
©
PQA
Tes*ng
Ltd.
The SoluGon
• What
was
needed
was
tes*ng
• The
solu*on:
• A
team
for
tes*ng
• An
augmen*ng
team

9. 7
©
PQA
Tes*ng
Ltd.
ResponsibiliGes
• Feature
Teams
• Tes*ng
new
features,
Demoing
new
features
• Troubleshoo*ng
and
fixing
• Ini*ally
–
applica*on
experts
hIp://washingmachinepro.com
©
PQA
Tes*ng
Ltd.
ResponsibiliGes
• Augmen*ng
Team
• Regression
Tes*ng
/
Integra*on
Tes*ng
• Tes*ng
new
features
in
SIT
• Become
applica*on
integra*on
experts

10. 8
©
PQA
Tes*ng
Ltd.
ResponsibiliGes
• Augmen*ng
Team
• Organizing
environment
needs
• Triaging
and
tracking
issues
• Communica*ng
with
end-­‐client
©
PQA
Tes*ng
Ltd.
ResponsibiliGes
• Augmen*ng
Team
• Working
smarter
• Fixing
communica*ons
processes
• Fixing
bug
triaging,
tracking,
fixing,
releasing
• Issue
tracking
• Implement
automa*on

11. 9
©
PQA
Tes*ng
Ltd.
Challenges
• Finding
knowledge
–
across
teams
• Chasing
issues
–
across
teams
• Knowing
issue
status
-­‐
communica*ons
(across
teams)
• Environments
–
coordina*ng
• Time
Zones
©
PQA
Tes*ng
Ltd.
Success!
• Feature
team
works
on
features
• Communica*on
process
streamlined
and
standardized
• Team
is
go-­‐to
expert
hIps://www.fromthegrapevine.com

12. 10
©
PQA
Tes*ng
Ltd.
Success!
• End
client
extremely
sa*sfied
• Less
issues
making
it
to
UAT
• Mee*ng
SLA’s
for
issues
• Mee*ng
communica*on
SLA’s
©
PQA
Tes*ng
Ltd.
Conclusions
• Agile
works
• But
it’s
not
always
the
simple
case
• Don’t
be
afraid
to
think
outside
of
the
box
• Some*mes
a
parallel
team
that
interfaces
is
your
solu*on
• Augment
your
tes*ng
team

13. 11
©
PQA
Tes*ng
Ltd.
Image
–
Sony
Pictures
Anima*on
2006
Ques*ons???