2. A little about me
Agile TesHng; 2009
More Agile TesHng: 2014
Agile TesHng CollecHon:
First agile team – 2000
Currently tester on Pivotal Tracker team
10. Structure discussions with a framework
• People moving, talking, wriHng on cards/sHckies/
• Mind map
• Impact map
• Flow diagram
• Context diagram
• Virtual for distributed teams
We’ll look at a few techniques
11. Common pitfall: Starting with “what”
1. PO writes story for feature:
• Describes implementaHon instead of purpose
and the problem to solve
• Leaves out the who, the users, quality aTributes
2. Team lacks shared understanding
3. Time wasted later in rework, adding in
4. Unhappy users
12. Start with the Why!
What is the purpose?
What value will it deliver?
• to end users?
• to the business?
How will we know it is successful?
from Gojko Adzic
28. Why and how we explore
Purpose: Learn info of interest/value to
customers, reduce risk, increase conﬁdence,
discover missing features, overcome our biases
Tools: Personas, roles, jobs, charters, tesHng
heurisHcs cheat sheet (Elisabeth Hendrickson),
Skills: curiosity, criHcal & lateral thinking,
observing, quesHoning - requires pracHce!
29. • Know your customers
• Make them real
• Role + job - think of all
• Plan your exploratory
tesHng around them
Picture – from Jeﬀ PaTon’s PragmaHc Personas
weekly column on SHcky Minds (1/25/2010)
What personas can you channel?
As a user, I want guidelines to
create a strong password, so
that I have limited risk for
• Draw and deﬁne a persona to
explore our story.
• Share with your pair. What
scenarios can you think of?
34. Other approaches for charters
“Analyze task funcHonality, and report on areas
of potenHal risk in refactoring tasks.”
Mnemonics: eg. SFDPOT - Structure, FuncHon,
Data, Plaworm, OperaHons and Time
42. Impact Mapping – Gojko Adzic,
• Why are we doing this? --- the goal
• Who can help or hinder? --- the stakeholders
• How can they help or hinder? --- the impacts!
• What can we do to help? --- the deliverables