On traditional projects, testers usually join the project after coding has started, or even later when coding is almost finished. Testers have no role in advising the project team early regarding quality issues but focus only on finding defects. They become accustomed to this style of working and adjust their mental processes accordingly. In agile, testers must collaborate closely with customers and programmers throughout the development lifecycle, where their focus changes from finding defects to preventing them. Janet Gregory shares ways to change the tester’s mindset from “How can I break the software?” to “How can I help deliver excellent software?”—a critical mental shift on agile projects. Another facet of the mind-set change is learning how to test early and incrementally. Janet uses interactive exercises and examples to help you understand how effective this mindset change is—and how you can apply it on your agile projects.

1. TJ
AM Tutorial
4/30/13 8:30AM
The Mindset Change for the Agile
Tester
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

2. 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.

3. 13/03/2013
April 2013
StarEast, Orlando
Janet Gregory, DragonFire Inc.
Copyright 2013
1
1

4. 13/03/2013
First agile team – 2000
Currently – coaching, testing
Book – Agile Testing; January 2009
Copyright 2013
DragonFire Inc.
3
• Some ‘Lecture’
• Some ‘Exercises’
• Handling questions ..
Copyright 2013
DragonFire Inc.
2

5. 13/03/2013
• Iteration (sprint)
• Feature (epic)
• Story
• Done (story done, feature done, release done)
• Feedback
Copyright 2013
DragonFire Inc.
5
• more than “just” testing code
• an activity; not a phase
Copyright 2013
DragonFire Inc.
6
3

6. 13/03/2013
What challenges do you see for agile testers?
Copyright 2013
DragonFire Inc.
7
4

7. 13/03/2013
Instead of
◦ We’re here to find bugs … or ensure
requirements are met … or break the
software …
Think
– What can I do to help deliver
the software successfully!
Copyright 2013
DragonFire Inc.
9
Can you think of some ways that you cross
boundaries in how you work?
Copyright 2013
DragonFire Inc.
10
5

8. 13/03/2013
• Simplicity
• Feedback
• Respond to change
Copyright 2013
DragonFire Inc.
11
Analytical
Relentlessly Curious
Observant
Skeptical
Empiricist
Critical Thinker
Investigator
http://www.slideshare.net/ehendrickson
Copyright 2013
DragonFire Inc.
12
6

9. 13/03/2013
What does this phrase mean to people?
Discuss at your tables,
and then we’ll debrief
Copyright 2013
DragonFire Inc.
13
T-shaped Skill-set
7

10. 13/03/2013
15
play, experiment, learn
keeps us vital and alive
16
8

11. 13/03/2013
• Gives us an enthusiasm for life that is
irreplaceable. Without it, life just doesn’t taste
good - Lucia Capocchione
• You can discover more about a person in an hour
of play than in a year of conversation. - Plato
• Play is our brain’s favourite way of learning –
Dianne Ackerman
Portia Tung (see references)
Copyright 2013
DragonFire Inc.
17
9

12. 13/03/2013
• Communication means ... sharing
◦ Ideas, information, decisions, solutions, etc.
• Collaboration means ...
◦ Working together to find solutions, etc.
◦ The ‘whole team’ …..
Customers, testers and programmers …..
Copyright 2013
DragonFire Inc.
19
• Power of Three
• 3 Amigos
• Pairing
• Continuous feedback
Copyright 2013
DragonFire Inc.
20
10

13. 13/03/2013
Picture by Augusta Evangelisti, based on diagram from Elisabeth Hendrickson
Explore
examples
User
Story
Accept
Story
High
level
AT
Fix
defects
Explore
Expand
Tests
Exploratory
Testing
Code
&
Execute
tests
Copyright 2013
DragonFire Inc.
Automate
tests
22
11

14. 13/03/2013
• Examples provide common language
• Shared common understanding
• Coding and testing concurrently
• Involves whole team
• Shared definition of DONE
• Prevents defects
Copyright 2013
DragonFire Inc.
23
• Question
• Elicit example
• Uncover hidden
assumptions
24
12

15. 13/03/2013
Checking:
◦ Confirmation
◦ Machine decidable
GUI
API
Unit Tests
Testing:
◦ Exploration & learning
◦ Requires sapience
**Definitions of testing vs. checking by Michael Bolton
Copyright 2013
DragonFire Inc.
26
13

16. 13/03/2013
27
It’s not just about code !!!
◦ Test assumptions
◦ Uncover hidden assumptions
The goal:
◦ Shared common understanding of the story
◦ Preventing defects (eliminate waste)
Copyright 2013
DragonFire Inc.
28
14

17. 13/03/2013
29
Iteration level
Story test level
System level
Release level
• Understand the
business needs
• What level are at?
• Collaborate
appropriately
Task level
Copyright 2013
DragonFire Inc.
30
15

18. 13/03/2013
31
• Know your
customers
• Make them real
• Plan your
exploratory testing
using them
• Picture – from Jeff Patton’s
Pragmatic Personas weekly column
on Sticky Minds (1/25/2010)
Copyright 2013
DragonFire Inc.
32
16

19. 13/03/2013
Legend
Good to Go
Some testing; could use more
Major issue
No testing done
Not applicable
17

20. 13/03/2013
• Know your context
• Have a tool box full
• Simple is often best
• Use your imagination
Let’s look at some examples
Copyright 2013
DragonFire Inc.
35
Taken from
Ready to use
Graphic
Organizers for
primary grade
teachers
18

21. 13/03/2013
Day 1
Day 1
Day 2
A new user
wants to
create her
account
The new user
wants to log
into the
system
An existing
user wants to
change her
password
An existing
user forgets
her password
The new user
wants to log
into the
system
Day ??
Day ??
Day 60
…….
The user
wants to
delete her
account
Day 30
The system
asks user to
change her
password
Day ??
…….
Words / Phrases
• I wonder ….
• What caught your
attention?
• Could you show me?
• What makes you think
there is more?
…….
Day 2
Day 2
Questions / Predictions
• What might happen
next?
• Why would that be?
• What is the worst thing
that could happen?
• …. or the best?
• What assumptions do
you have?
19

22. 13/03/2013
Block
account
User can’t
log in
User
enters
wrong
password
They are in
the
database
Wrong
password a
2nd time;
Issue
warning
The
credentials
meet
req’ts
Wrong
password a
third time
Prevent
user from
logging in
again;
Display
msg
They
entered
their
credentials
correctly
Their
password
expired ….
Copyright 2013
DragonFire Inc.
39
• Practice anticipating what will happen
• Define your tests
• Check – running tests or collaborate with
customers and programmers before* coding
• Be prepared to change your tests if your
predictions are wrong
• Learn by reviewing – what questions could
you have asked first.
Copyright 2013
DragonFire Inc.
40
20

23. 13/03/2013
rules
Sub topic
rules
user name
save
password
Sub topic
first time
Sub topic
encryption
MAIN
new account
TOPIC
Sub topic
change
Sub topic
Login : User name & password
Copyright 2013
DragonFire Inc.
42
21

24. 13/03/2013
• Think simple
• Have a variety of tools
• Adapt to your needs
• Look in places you may not have considered
Copyright 2013
DragonFire Inc.
43
22

25. 13/03/2013
• Curiosity
• Ability to observe
• Ability to challenge
• Ability to adapt
• To recognize contexts
• Ability to THINK !
Copyright 2013
DragonFire Inc.
45
Challenge
Yourself !
46
23

26. 13/03/2013
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
Copyright 2013
DragonFire Inc.
47
• Elisabeth Hendrickson
CAST keynote http://www.slideshare.net/ehendrickson
Explore It! – new book on Pragmatic Programmers
• Ben Kelly, http://lets-test.com/wp-content/uploads/2012/05/LetsTest2012BenKelly-TheTestingDead.pdf
• Markus Gartner, http://www.shino.de/2012/07/16/cast-2012-the-testing-dead/
• Paul Carvalho, http://www.agilejournal.com/articles/columns/columnarticles/6515-low-tech-tools-for-the-thinking-tester
• Michael Bolton, http://www.developsense.com/blog/2009/08/testing-vschecking
• Ready to Use Graphic Organizers
24

27. 13/03/2013
• http://www.exampler.com - Brian Marick’s web site
• Gojko Adzic, Bridging the Communication Gap, 2009; Specification by
Example, 2011
• www.stickyminds.com/ Pragmatic Personas - Jeff Patton’s weekly
column 1/25/2010
• Jean Tabaka, Collaboration Explained, 2006 Addison-Wesley
• http://www.uie.com/articles/indispensable_skills
• Portia Tung – Power of Play
http://www.selfishprogramming.com/category/playmaking/
• Ester Derby and Dianne Larsen, Agile Retrospectives
25