This document outlines Joel Montvelisky's presentation on communication and testing. It discusses how communication is typically handled in testing by simply providing status updates and reports, but fails to align with goals. The presentation introduces a four level model of testing communication: over-the-wall, learning, research, and constructive. Over-the-wall communication examples include bug reports and test results, with the objective of helping stakeholders make tactical decisions. The model aims to improve alignment of communication with goals at different levels.
%+27788225528 love spells in Atlanta Psychic Readings, Attraction spells,Brin...
Communication and Testing: Why You Have Been Wrong All Along!
1.
T23
Personal
Excellence
5/11/17
15:00
Communication
and
Testing:
Why
You
Have
Been
Wrong
All
Along!
Presented
by:
Joel
Montvelisky
PractiTest
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.
Joel
Montvelisky
Joel
Montvelisky
is
the
chief
solution
architect
and
QA
manager
at
PractiTest,
where
among
other
things
he
works
with
hundreds
of
organizations
worldwide
to
improve
their
testing
and
most
importantly
their
testing
results.
During
the
past
twenty
years
he
has
been
a
tester,
QA
manager,
and
consultant/trainer
for
companies
in
Israel,
Europe,
and
the
United
States.
Joel
is
the
cofounder
of
a
number
of
cool
testing-‐related
projects
such
as
the
Annual
State
of
Testing
Report
and
the
OnlineTestConf,
and
publishes
his
thoughts
on
QA
and
testing
on
his
QABlog.practitest.com.
Contact
Joel
at
joel@practitest.com.
3. Communica)on
Skills
for
Testers
and
Why
you
have
been
doing
it
wrong
all
this
)me…
Joel
Montvelisky
Chief
Solu)on
Architect
4. What
we
want
to
cover
today?
Communica)on
&
Tes)ng?
What
is
Communica)on?
Typical
Tes)ng
Communica)on
4
Levels
of
Tes)ng
Communica)on
Model
SMART
and
FOCUSED
Communica)ons
Q&A
1
2
3
4
5
6
Meetup Series
5. Who
am
I?
Professions
:
(last
20
years)
-‐
Accidental
Tester
-‐
QA
Manager
-‐
Blogger
-‐
Speaker
-‐
Solu)on
Architect
Prac)Test:
-‐
Chief
Solu)on
Architect
-‐
QA
Manager
Other
Projects:
-‐
OnlineTestConf
-‐
State
of
Tes)ng
Meetup Series
6. About
✓ SaaS
ALM
Solu)on
✓ Simple
&
Intui)ve
–
yet
–
Professional
&
Flexible
✓ Integrates
with
Jira,
Selenium,
Jenkins,
Pivotal
Tracker,
QTP,
Bugzilla,
Ranorex,
SoapUI,
etc…
✓ Best
Darn
Support
in
the
Business
☺
Meetup Series
9. To
provide
informa(on
about
the
project
and
product
so
that
the
stakeholders
can
make
the
correct
decisions.
Why
do
we
Test?
Meetup Series
10. To
provide
informa(on
about
the
project
and
product
so
that
the
stakeholders
can
make
the
correct
decisions.
Why
do
we
Test?
Meetup Series
11.
12. Why
communica)on?
Meetup Series
76% Very Important
23% Important
67% Very Important
31% Important
78% Very Important
21% Important
72% Very Important
26% Important
14. What
is
communica)on?
Every
communica)on
event
is
defined
by
four
components:
Meetup Series
15. What
is
communica)on?
The
Goal
The
Players
• Sender
• Receiver/s
The
Channel
(encoding
-‐
medium
-‐
decoding)
The
Message
In
Theory,
we
think
of
Communica)on
like
this…
Every
communica)on
event
is
defined
by
four
components:
1
2
3
4
Meetup Series
19. What
is
Communica)on
Alignment?
Communica)ng
while
focusing
on
the
GOAL!
We
need
to
ask
ourselves
3
important
ques)ons:
– What
do
we
want
to
achieve?
– Who
is
sending
and
receiving
the
message?
– What
channel
should
we
use?
Meetup Series
21. Typical
Tes)ng
Communica)on
Bugs
Release
Notes
Test
Plans
Tes)ng
Summary
Reports
Status
Updates
&
Dashboards
Meetup Series
Test
Reports
22. The
main
problem:
As
testers,
we
don’t
stop
Align
our
communica)on
with
the
GOALs
we
want
to
achieve.
Typical
Tes)ng
Communica)on
We
limit
Tes(ng
Communica(on
to
upda(ng
“everyone”
on
the
status
of
our
tes(ng,
when
we
could
be
achieving
a
lot
more...
Meetup Series
24. Four
Levels
of
Tes)ng
Communica)on
Model
4
Meetup Series
25. Construc)ve
Communica)on
Research
Communica)on
4
Levels
of
Tes)ng
Communica)on
Learning
Communica)on
Over
the
Wall
Communica)on
Meetup Series
26. 4
Levels
of
Tes)ng
Communica)on
Level
1:
Over
the
Wall
Communica)on
Over
the
Wall
Communica)on
Meetup Series
27. 4
Levels
of
Tes)ng
Communica)on
Level
1:
Over
the
Wall
Communica)on
Examples
¤
Bug
Reports
/
Lists
¤
Tes)ng
Results
/
Reports
¤
Update
Presenta)ons
/
Emails
Objec.ve
Help
stakeholders
with
their
tac)cal
decisions.
Characteris.cs
¤ One
way
communica)on:
“Fire
&
Forget”
¤ Dry
and
fact
based
¤ “One
Size
Fits
All”
templates
Biggest
problem
¤
Most
of
)mes
we
don’t
provide
any
new
informa)on
or
real
help.
¤
It
enrages
more
than
it
helps.
Over
the
Wall
Communica)on
Meetup Series
28. 4
Levels
of
Tes)ng
Communica)on
Level
1:
Over
the
Wall
Communica)on
Over
the
Wall
Communica)on
Meetup Series
1. Make sure this is not your only communication activity!
2. Automate as much as possible
3. Use it mostly as a basis for measurements
29. 4
Levels
of
Tes)ng
Communica)on
Level
2:
Learning
Communica)on
Learning
Communica)on
Meetup Series
30. 4
Levels
of
Tes)ng
Communica)on
Level
2:
Learning
Communica)on
Examples
¤
Reqs
&
Design
Review
Mee)ngs
¤
1-‐on-‐1
mee)ngs
with
Dev
or
Product
¤
Sessions
with
other
tes)ng
teams
Objec.ve
¤ Beger
understanding
of
the
AUT
¤ Create
awareness
of
tes)ng
in
Dev
&
Product
teams
Characteris.cs
¤ Mainly
inbound
communica)on
¤ Around
concrete
and
simple
informa)on
of
product
and
risks
¤ Introduces
some
stakeholders
to
the
tes)ng
process
The
Good
and
Bad
¤
Great
first
step
to
get
informa)on
from
addi)onal
stakeholders.
¤
Most
)mes
it
misses
the
chance
to
get
these
stakeholders
more
involved
in
the
tes)ng
process.
Learning
Communica)on
Meetup Series
31. 4
Levels
of
Tes)ng
Communica)on
Level
2:
Learning
Communica)on
Learning
Communica)on
Meetup Series
1. Focus it on your internal needs only
2. Close to no value for other teams or stakeholders
3. You will need to jump very quickly to the next level!
32. 4
Levels
of
Tes)ng
Communica)on
Level
3:
Research
Communica)on
Inves)ga)ve
Communica)on
Meetup Series
33. 4
Levels
of
Tes)ng
Communica)on
Level
3:
Research
Communica)on
Examples
¤
Mee)ngs
with
Support
to
analyze
)ckets
¤
Mee)ngs
with
Pre-‐Sales
or
Tech-‐Sales
¤
User
Profiles
(Personas)
¤
Compe)tor
Profiles
¤
Sessions
with
higher
management
Objec.ve
¤
Get
more
complex
informa)on
on
the
AUT.
¤
Understand
what
informa)on
is
needed
by
stakeholders
that
can
be
provided
by
tes)ng.
Characteris.cs
¤
2
way
communica)on
channel
–
Expect
more
ques)ons
than
informa)on.
¤
Provides
addi)onal
tes)ng
ideas,
not
necessarily
related
to
func)onality.
¤
Usually
surprises
people
when
you
come
and
ask
for
a
mee)ng
–
Surprises
are
good!
The
good
and
the
bad
¤
Provides
valuable
informa)on
on
non-‐
func)onal
stuff
from
Real
Life
Users.
¤
Awakes
interest
from
addi)onal
stakeholders
in
the
tes)ng
process.
¤
Generates
noise
from
the
outside.
Inves)ga)ve
Communica)on
Meetup Series
34. 4
Levels
of
Tes)ng
Communica)on
Level
3:
Research
Communica)on
Inves)ga)ve
Communica)on
Meetup Series
1. It will throw you to the political arena of your company –
be ready
2. Make sure to provide value to your immediate teams
3. People will criticize your deliverables, be careful and
precise
35. 4
Levels
of
Tes)ng
Communica)on
Level
4:
Construc)ve
Communica)on
Meetup Series
36. 4
Levels
of
Tes)ng
Communica)on
Level
4:
Construc)ve
Communica)on
Examples
¤
Pair
tes)ng
sessions
with
Dev
&
Support
engineers
¤
Test
Planning
workshops
with
representa)ve
from
different
teams
¤
Visits
or
sessions
with
Strategic
Customers
or
CABs
to
understand
their
usage
Objec.ves
¤
Get
and
share
informa)on
and
involvement
with
internal
stakeholders
¤
Generate
recogni)on
on
the
value
of
tes)ng.
¤
Get
first
hand
informa)on
from
users
and
the
field.
Characteris.cs
¤
2
way
communica)on
¤
Internal
and
external
players.
¤
Requires
advanced
skills
of
communica)on
and
group
management.
¤
Generates
more
involvement
into
the
tes)ng
process.
The
good
and
the
bad
¤ Generates
recogni)on
on
the
value
of
tes)ng
¤ Requires
tons
of
prepara)on
and
execu)on
¤ This
is
a
long
range
gain
and
a
short
range
investment.
Construc)ve
Communica)on
Meetup Series
37. 4
Levels
of
Tes)ng
Communica)on
Level
4:
Construc)ve
Communica)on
Construc)ve
Communica)on
Meetup Series
1. 50% process – 50% content
2. Tons of politics, specially when working with sales and
customers
3. Many times the fruits of this level are long range!
41. ¥
Simple
-‐
Graphs
over
Words
/
One-‐liners
over
Paragraphs
¥
Measurable
-‐
Numbers
&
Stats
over
feelings
and
descrip)ons
¥
Ac)onable
-‐
Suggest
solu)ons,
don’t
stop
at
poin)ng
at
issues
¥
Repeatable
-‐
Show
informa)on
over
versions
and
products
¥
Timely
-‐
Inform
while
s)ll
relevant
S.M.A.R.T.
Communica)on
Meetup Series
42. ¥
Fast
-‐
Be
quick
to
answer
ques)ons
¥
Objec)ve
-‐
Share
good
and
bad
news
equally
¥
Condensed
-‐
To
the
point
and
quickly
¥
User
centered
-‐
Think
on
the
needs
of
each
(not
all!)
of
your
users
¥
Service
-‐
The
customer
is
always
right!
F.O.C.U.S.
Approach
Meetup Series
43. To
summarize
Communica)on
is
a
complex
mechanism
There
are
many
goals
testers
don’t
even
try
to
achieve
via
correct
communica)on
use
There
are
a
number
of
levels
of
communica)on
you
can
use
(smartly!)
to
advance
your
goals
Communica)on
should
be
SMART
&
FOCUSed
1
2
3
4
Meetup Series
