From qu
alit
y
a
ssur
ance
t
o
qu
alit
y
a
ssis
t
ance
Go
jk
o
Adzic @go
jk
o
adzic go
jk
o.net
SQ
A
D
a
ys 24, Mosco
w
80': $500.000 f
or Pro
je
ct
Mana
gement
sof
t
w
are
E
arl
y
90': sof
t
w
are f
or
the
ma
sse
s
Mid 90': rise of
sof
t
w
are
engineering
L
a
te 90's:
army
of
te
s
ters
E
arl
y
00's:
te
s
ting is
t
oo
expensive... let
's send it
somewhere che
aper
Mid 00's: it
's
a
ctu
all
y
t
oo
slo
w
... let
's
a
ut
oma
te it
L
a
te 00's: s
till
t
oo slo
w
...
let
's share
the
re
sponsibilit
y
"Our pe
ople don’
t
jus
t
te
s
t
our products;
they
ha
ve
a
much bro
ader mission
t
o
influence
all
te
am members
t
o
t
ake re
sponsibilit
y
f
or
qu
alit
y
.
"
ht
tps:/
/
te
chblog.king.com/wha
t
-doe
s-q
a
-s
t
and-for-
a
t
-king/
Mid 10's: qu
alit
y
a
ssur
ance
a
ssis
t
ance
"
a
t
WordS
t
ar, ba
ck
in
1983... I
w
a
s
able
t
o
convince
them
t
o change
the name, from Qu
alit
y
A
ssur
ance
t
o Qu
alit
y
A
ssis
t
ance.
"
-- Cem Kaner,
The Ongoing Rev
ol
ution in Sof
t
w
are
Te
s
ting
ht
tp:/
/w
w
w
.kaner.com/pdfs/
The
OngoingRev
ol
ution.pdf
A
tl
a
ssian: 6 Q
A
engineers suppor
t
100 pe
ople
“No
t
my
job!”
“
Wha
t
is
the role of
te
s
ting?”
Wha
t
is
the role of
te
s
ting?
Help
the
te
am mo
ve
f
a
s
ter,
with more
confidence
1. Find
the feeling
2. Shrink
the change
3. Gro
w
y
our pe
ople
“Pe
ople change...
be
ca
use
they
are
sho
wn
a
truth
tha
t
influence
s
their
feelings”
John P. Cotter, Heart of Change
S
tep
1: Sell
the
problem, no
t
the
sol
ution
More
tr
aditional
things
t
o sho
w
»
End-to-end delivery cycle speed
»
Waiting time for tasks
»
Amount of rework
»
Satisfaction
“Pe
ople don’
t
re
sis
t
change;
they
re
sis
t
being changed.
”
Peter Senge
S
tep
2: Inv
ol
ve
the
te
am in proposing
sol
utions
S
tep
3:
Aim f
or small,
reversible
experiments
So,
wha
t
do
te
s
ters
do no
w?
So,
wha
t
do
te
s
ters
do no
w?
shrink
the change
gro
w
y
our pe
ople
So,
wha
t
do
te
s
ters
do no
w?
shrink
the change
make
te
s
ting e
a
sier
gro
w
y
our pe
ople
te
a
ch o
thers
t
o
te
s
t
F
our levels
1. Deliver
y
t
a
sk/s
t
or
y
2. Fe
a
ture
3. Product
4. Organisa
tion
A
t
deliver
y
t
a
sk/s
t
or
y
level
»
teach people to ask better questions
»
heuristics
»
taxonomies
»
boundary analysis
»
risk review
»
in-progress feedback
Tr
y
... f
ocus
te
s
ters on highe
s
t
risk
Developers must do all other tests, but can ask for
advice
Tr
y
... Pre-development
te
s
ting
no
te
s
Write short notes on the types of bugs expected to
see for this a type of task
Tr
y
... Q
A
Kick
off
Pair with developers to brainstorm testing notes
Tr
y
... Developer on
Te
s
t
Developers take turns to perform most testing tasks
Tr
y
... Que
s
tion che
cklis
t
A pre-agreed list of things developers can ask from a
tester...
Example... (1:15)
1.
What are you going to test around feature X. I'll
check that before I hand it over to you
2.
I've checked A, B and C - is there anything more I
should do before we call this ok?
3.
X is really hard to test - can you help me out
Marcus Hammarberg, ht
tp:/
/marcusoft
.net
Tr
y
... feedba
ck
exercise
s
Propose boundary conditions, let everyone write down
what the system should do in those cases
Tr
y
... Q
A
Demo
Review progress with developers and provide risk/
testing ideas
Tr
y
... cross-functional
a
ut
oma
tion
t
ools
Testers participate in defining the test, developers
automate
A
t
a
fe
a
ture level
»
help people get into situations where they can be
surprised
»
teach exploratory testing
»
teach people how to discover tangential
information
Tr
y
... p
aired explor
a
tion
Explore together with a developer, switching between
driver and observer
Tr
y
... blitz
te
s
t
Short period when the whole team works together,
trying to break a feature
Tr
y
... Risk
s
t
orming
Group analysis of risks if the feature is broken, and
ideas how to mitigate it
Tr
y
... dogf
ooding
Use latest features internally before your users
Tr
y
... spe
cifica
tion by
example
Collaborative analysis, capture acceptance criteria
through key examples and document for automated tests
A
t
a
product
level
»
reduce testing friction
»
build up dashboards
»
improve system observability
»
introduce control points
Tr
y
... Bug review
s
Root cause analysis, review and learn from bugs
Tr
y
...
A
CC Ma
trix
Shared agreement on risk, mapping capabilities to
components and quality attributes
Tr
y
...
te
s
ting
t
ours
A variety of time-boxed exploration plans.
Tr
y
...
w
a
s
te snake
People record where they lose time unproductively,
periodically review and adjust process/tooling
Tr
y
... build small
contex
tu
al
t
ools
Speed up test setup or data collection
A
t
an organisa
tional
level
»
speed up idea spreading
»
organise cross-team sharing
»
internal consulting
»
don't fix people's tests, fix their process
Tr
y
... ro
t
a
te
a
cross
te
ams
Let testers change teams relatively frequently
Tr
y
...
Te
s
ting on
the
T
oilet
Google test experts wrote fliers about testing
topics, then plastered them on bathroom walls.
Tr
y
... FixIt
d
a
ys
Volunteers organize one day events to address
important, but not urgent issues
Tr
y
...
Te
s
ting f
air
Show off latest tools and techniques to the rest of
the organisation
Mike Bl
and's R
ainbo
w
of
De
a
th
model
»
Intervene
»
Validate
»
Inform
»
Inspire
»
Mentor
»
Empower
ht
tps:/
/mike-bl
and.com/
the-rainbo
w
-of-de
a
th
ht
tps:/
/mike-bl
and.com
From quality assurance to quality assistance
