Testing is an attitude which brings us to trust results based on the fact that we can validate them. Testing is an approach which allows us to think about how to verify we did the right thing even before starting. Testing is a practice which allows us to write effective tests that can be repeated indefinitely while systematically producing consistent results. Agile is built around the idea of managing complex projects, recognizing the importance of emerging results and verifying in a very disciplined way the assumptions and hypothesis we make as often and as thoroughly as possible. This means testing everything we do, every day ... So if you are truly Agile, you are living testing in every second of your life!

1. Agile Testing is nonsense
because Agile it’s all about testing…
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

2. Andrea Tomasini
Agile Coach & Trainer
andrea.tomasini@agile42.com
@tumma72
@agile42/coaches
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

3. Agile Testing is nonsense, because Agile is Testing
Testing is an attitude which brings us to trust results based
on the fact that we can validate them. Testing is an
approach which allows us to think about how to verify we
did the right thing even before starting. Testing is a
practice which allows us to write effective tests that can be
repeated indefinitely while systematically producing
consistent results.
!
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

4. Agile Testing is nonsense, because Agile is Testing
Agile is built around the idea of managing complex projects,
recognizing the importance of emerging results and
verifying in a very disciplined way the assumptions and
hypothesis we make as often and as thoroughly as
possible. This means testing everything we do, every
day … So if you are truly Agile, you are living testing in every
second of your life!
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

5. Testing as an Attitude...
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

6. attitude: a settled way of
thinking or feeling about
something: he was questioned
on his attitude to South Africa |
being competitive is an
attitude of mind .
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

7. Agile Values & Principles
Agile Values & Principles are supporting teams developing
the right attitude to enable continuos and regular value
delivering to the client, while continuously improving
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

8. Individuals & interactions
Working software
Customer collaboration
Responding to change
o
v
e
r
Processes & tools
Comprehensive documentation
Contract negotiation
Following a plan
We recognize
the value here...
We value
this more….
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

9. Empirical Process Control
Switching from measuring compliance to measuring
outcome
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

10. Defined Process Control
agile42 | We advise, train and coach companies building software
The time required to complete a
repeatable action is a valid proxy to
predict time to finish the whole
www.agile42.com |
All rights reserved. Copyright © 2007 - 2010.

11. 8!
6
20
5s
80?
agile42 | We advise, train and coach companies building software
38
10s
76?
52
15s
www.agile42.com |
69?
20s
All rights reserved. Copyright © 2007 - 2009.

12. Empirical Process Control
agile42 | We advise, train and coach companies building software
Every step performed while
creating a new product is unique,
only outcome can be trusted
www.agile42.com |
All rights reserved. Copyright © 2007 - 2010.

13. Iterative and incremental
Stop assuming you already know what the client wants and
discover it while building it together
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

14. I need to move from A to B faster than by
walking…
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

15. I am not that good at staying in equilibrium,
I need something more stable…
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

16. I am stable now, but not fast as I would
like to be, can we go faster?
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

17. I figure I am pretty tired in the evening, and
though I like sport, I still need to be faster
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

18. What is this?
Inspect the outcome and
learn to validate your
assumptions & hypothesis
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

19. BUT… not Because clients do not
trust that their money has been
used wisely...
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

20. What you get as a result…
ice-cream!
Ad-Hoc Tests
User Acceptance Tests
Integration Tests
Unit Tests
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

21. Testing as an Approach...
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

22. approach: a way of dealing with
a situation or problem: we need
a whole new approach to the
job.
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

23. Experimenting new things, innovating, requires
dedication and commitment…
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

24. We like to learn using short feedback loops
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

25. Sometimes we succeed in
validating our hypothesis...
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

26. Sometimes we don't...
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

27. Why are we
thinking about
what to test and
how to test it
beforehand?
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

28. Reduce... Social Risk
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

29. Reduce... Schedule &
Cost Risks
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

30. Reduce... Business Risks
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

31. Reduce... Technical Risk
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

32. With every
step we want
to learn
something...
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

33. Testing as a Practice...
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

34. practice: the actual application
or use of an idea, belief, or
method, as opposed to theories
relating to it: the principles and
practice of teaching | the
recommendations proved too
expensive to put into practice.
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

35. Creating a Vision with Stakeholders
Peter Senge, Vision Strategies
Co-Creating
Collaboration
Consulting
Testing
Selling
Telling
Effort
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

36. As a Returning Customer, I
want to jump with one
click to the checkout page,
so that I can purchase
Agile Teams normally
work with User
Stories to agree
what needs to be
built and how…
good quicker
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

37. - Detail about payment are
visible
- Shipping address is visible
- I can change quantity of
the items
User Stories do have
Acceptance Criteria
on their back, Team
wouldn't commit to
them, without
knowing when they
would be considered
finished
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

38. Backlog
Definition
Shippable
of Ready
Product
Definition
of Done
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

39. Continuous Improvement
Agile Team achieve continuous improvement by deciding
how to Test a new behavior or practice, even before
starting introducing a change…
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

40. (無理: muri)
Overburden
do not overload your
People
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2010.

41. Unnecessary
Variations
(斑: mura)
agile42 | We advise, train and coach companies building software
keep the Flow
Even
www.agile42.com |
All rights reserved. Copyright © 2007 - 2010.

42. Wasteful
Activities
(無駄: muda)
remove non value adding
Activities
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2010.

43. Agile Teams
also test
their
behavior
constantly...
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

44. ... and learn
how to get
better over
time...
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

45. ... BUT it's not about finding
who's right and who's wrong!
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

46. Capturing
behavior and
motivation
helps teams to
measure their
effectiveness
agile42 | We advise, train and coach companies building software
Working Agreements
1.
We want to pair when stories
are bigger than 2 points, so
that we reduce risk
2. We want to work with ATDD
on all stories, so that we will
have a cleaner design
3. ...
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

47. Toyota Kata
& Lean A3
are very
powerful
together…
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2010.

48. Keep
Goals & Try
Working Agreements
1.
We want to pair when stories
are bigger thanDefinition of Done
2 points, so
✓ Integrated in the staging
that we reduce risk
2.
3.
system
We want to work with ATDD
Definition of Ready
✓ all acceptance criteria are
on all stories, so that we will
✓ User Story format
fulfilled
have a cleaner design✓
Max 5pt.
✓ no regression
...
✓ INVEST
✓ PO has seen the story
✓ At least 2 Acceptance Criteria
✓ Performance ok
Doing TDD
on everything
Next: TDD
on one story
1 size > estimated
90% coverage of
the code
Accelerators
ard
TDD on h
story
Breaks
Delay wit
h
designers
agile42 | We advise, train and coach companies building software
d
All Stories worke
with TDD
No extra effort
re
for infrastructu
Active Learning
Cycle provides
guidance on
what to change
and what to
expect from
the changes…
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

49. f- d
el ze
s
i
an
rg
o
managed
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

50. Focu
s
on va
lue
Pull
on
ti
ra
Team
agile42 | We advise, train and coach companies building software
om
pe
ti
ti
nce
lia
mp
C
C
sh
Co
lla
o
bo
Pu
on
Individual
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

51. Actuality
Agile
Values &
Principles
Cultivation
Control
Competence
Possibility
agile42 | We advise, train and coach companies building software
Impersonal
People
Collaboration
William Schneider - The four Core Cultures
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

52. e
Ma
na
g
if
ba t t
h
la
nc e
e
Beliefs
Le
sh
Culture
Actions
ad
Results
coaching is an ongoing
long term investment
Experiences
The “Results Pyramid” is copyright of Partners in Leadership LLC
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

53. How do we know if this is working for us?
Necessary Condition (NC), is
what is needed in order to
fulfill the Success Factor
Goal
Represent the Goal
we want to achieve
PSF
NC
Possible Success Factor (PSF)
represent a hypothesis about a
“factor” that would allow to
achieve the Goal
agile42 | We advise, train and coach companies building software
Agile Strategy Map ™
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

54. How can we make sure we are not missing
something?
To verify the hypothesis we define what
is needed in order to start a pilot aiming
at verifying the validity of the PSF#1
NC#1.1: we need to list at least 3 projects
per product area
NC#1.1.1: we need to chose projects and
define comparable dimensions such as:
business value, impact, (cost?)
NC#1.2: we need to define a sample
Portfolio funnel, and check that Teams
can deliver with the provided information
agile42 | We advise, train and coach companies building software
NC#1.2
Goal
PSF#1
NC#1.1
NC#1.1.1
PSF#1: we believe that by
consolidating all projects in one
Portfolio, we will be able to make
better business decisions
www.agile42.com |
Agile Strategy Map ™
All rights reserved. Copyright © 2007 - 2009.

55. Ok, it worked… now what’s next?
The Pilot was successful...
The Success Factor,
NC#1.2
becomes Critical (CSF)
NC#1.1
Goal
CSF#1
NC#1.1.1
CSF#1: we have to consolidate
all projects in one Portfolio, so
that will be able to make better
business decisions
agile42 | We advise, train and coach companies building software
www.agile42.com |
Agile Strategy Map ™
All rights reserved. Copyright © 2007 - 2009.

56. 1. Testing is an attitude,
because if we embrace the
Agile Manifesto and its
principles, we have to
accelerate learning, and this
requires individual
commitment to validate
assumptions
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

57. 2. Testing is an approach, it
requires to systematically
initiate everything we do by
understanding the
constraints, the expected
outcomes, and the possible
learnings
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

58. 3. Testing is a practice,
because once we develop the
attitude and learned the
approach, we will be able to
emerge practices, which will
make us more effective at
learning
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

59. 4. Everybody makes mistake,
every mistake is an
opportunity to learn, and we
need to be ready to learn and
capitalize on that experience.
If we are not, it will be just a
failure!
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

60. 5. Testing is a Team
responsibility. Stay away from
boxing responsibilities into
roles… you will hinder selforganization and shared
commitment
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

61. k
n
a
h
T
!
u
o
Y
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

62. More food for thought...
http://slideshare.net/tumma72
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.

63. Copyrights notice
All material produced in this presentation is protected by the
Creative Common License 3.0 (by-nc-sa).
agile42 | We advise, train and coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2009.