are you building the right thing? - janet g @ cmbagileconf 2016
TRANSCRIPT
Agile Development
Agile Colombo, Sri Lanka 2016
Janet Gregory
@janetgregoryca
www.janetgregory.ca
Are You Sure You’re Building the Right Thing?
Copyright 2016 Janet Gregory, DragonFire Inc.
Agile Testing; 2009
More Agile Testing: Oct 2014
Website:
www.agiletester.com www.agiletester.ca
2
Ideas for building quality in …..
that you can start using tomorrow
Take-aways
3
How do we define quality?
4
"Quality is value to some person.” – Jerry Weinberg
For your value, which is better?
Which is right?
Deming’s Third Principle
Cease dependence on inspection
(testing after product is built)
Instead, build quality into the process
In agile development, the focus is on
Prevention(i.e. build quality in)
not Detection
7
Common pitfall: Starting with “how”
Product Owner writes a story for a feature
And describes the implementation instead
of purpose and the problem to solve
8
Can something be right? But not meet a customer’s needs?
Or … We might overlook stakeholders
Each feature may have multiple, different users
10
The Risks
11
Wasted time in rework
Time added for missing
requirements
Result: Unhappy Users
12
Look at the big picture
What can we do?
1. Find a pair
2. One person faces away from the screen
3. The other person will have 2 -3 minutes to describe the picture I show next
4. When I say stop, turn around and discuss any differences in what was described.
Achieve Shared Understanding
16
Getting everyone engaged
17
BusinessAnalyst Designer
?????
Keep the big picture in mind
Start with the Why!
19
What is the purpose?
What value will it deliver?
• to end users?
• to the business?
How will we know it is successful?
Use a framework to structure discussions
20
Mind map
Diagram flows
Create mock-ups
Let’s look at some other examples
Story MappingJeff Patton: User Story Mapping
21
Story Mapping
Steve Rogalskyhttp://winnipegagilist.blogspot.ca
More Agile Testing, p. 12822
Structured Conversations
23
functional
nonfunctional
www.DiscoverToDeliver.com/visual-language.php
Source: Discover To Deliver, Gottesdiener & Gorman, 2012
25
Example mapping - discovery workshops
Source: Matt Wynne: Introducing Example Mapping
As the security dude, I want to enforce strong password rules for customer log-in, So that we have limited risk for identity theft
Example
26
Story
Rules
Examples
Questions
1. At least 8 characters long2. Maximum of 32 characters3. Contains at least 1 special char and 1 number
Valid: p4ssw0rd!, pa55w#rdpInvalid: P4ssw0rd1, p4ssw@d
Where to put focus if an invalid password is entered?What happens if they have a certain number of invalid passwords?
• To elicit requirements
• To reduce uncertainty
• To test people’s understanding of the requirement
27
Use examples ….. Credit and thanks to Brian Marick
Examples …..
• Can become the actual tests
• Are a form of specification
Building the right thing ….. means
Creating a shared understanding first
28
We also need to explore what we built
29
Use what
you
learned
Measure
/ Evaluate
Learn
Build
30
Development in agile projects is not easy
• Problems happen faster so impact is felt faster
• Make the issues visible so you can learn
• Be courageous – be a change agent
Mostly, have fun and enjoy the
challenge!
31
More reading
32
• Gottesdiener, Ellen and Mary Gorman, Discover to Deliver, 2012
• Hendrickson, Elisabeth, Explore It!, 2013
• Larsen, Michael, “Unchartered Waters”, http://bit.ly/1NMYyww
• Patton, Jeff, User Story Mapping, 2014
• Simbhoedatpanday, Kishen, “Example Mapping – Steering the Conversation”, http://bit.ly/1Qlnz0y
• Wynne, Matt, "Introducing Example Mapping", http://bit.ly/1iw19w4
Contact Information
www.janetgregory.ca
twitter: @janetgregoryca
www.lisacrispin.com
twitter: @lisacrispin
www.agiletester.ca
www.agiletester.com33