Many of the customers I am speaking with are dealing with two mayor developments. First, there is a very strong urge to reduce costs in general and cost and speed of testing in particular. The other trend is of course being agile. Combining the two trends I conclude that we testers need to improve the efficiency and quality of our work. I believe enriching our toolkit with better techniques, tools and methods will help us to do so. Since the traditional test design techniques are quite powerful, our quest for new techniques should focus on those that helps us to be more efficient in an agile context. During the session I will give examples of techniques, tools and methods that are already available in other disciplines and explain how they can be useful for us. One of the sources I'll use is the agile extension of the BABOK guide, The Business Architects Body of knowledge contains a rich source of valuable techniques. I'll distinguish between techniques that we need to actually design and perform our tests, create error situations and detect errors. And on the other hand supporting techniques that help us to determine scope, improve our process and moderate efficient sessions with our team. Examples I'll give include: How to provoke and recognize errors, Story decomposition, Story mapping, Value stream mapping, using persona's, Business Capacity Model, Subway mapping, Process simulation and Gaming. The presentation will suggest techniques, tools and methods that can be used by the participants straight away. The presentation will make you aware that valuable techniques are already available in various sources. I'll introduce a classification model helps them to seek and recognize additional techniques. These techniques enable testers to show their other face: participating in and moderating sessions and coach team members with using the right tools/methods.

1. Efficiency with the right
techniques, tools & methods
Derk-Jan de Grood
Belgium Testing Days 2014
1

2. My 1st Pocket knife
2

3. 3

4. 4

5. 5
Definition tool

6. 6

7. 7

8. 8
The wrong tool…

9. 9

10. Searching for tools
10

11. 11
What do we do when testing?

12. 12
Analyse

13. 13

14. 15
Challenge

15. 16
James Wittacker

16. 17

17. Some examples
Reduce the bandwidth of the network connection
Make the network fail
Limit the disk space available for the application
Interruptions
SQL statement injection
Searching for overflows (256, 1024, 32767, etc…)
Change the order of activities
18

18. Think, Challenge and Observe
20
Observe

19. Test Recognition Techniques
21
Inconsistencies: external
Extras

20. Searching for tools
Test Design
Error Creation
Error Detecting

21. Two Trends
23

22. 24

23. Agile testing Characteristics
25
• Cooperation and teamwork
• Variety in cooperation and workshops
• Roles merging and testers get involved
into design and development
• Automated or Exploratory testing
• Keep track on progress and quality

24. Test Design
Error Creation
Error Detecting
Focus
(Scope & Prio)
GRIP
(Planning&Control)
Test
Improvement
Facilitation
Methods
Searching for tools

25. 27
The IIBA- BABOK guide…

26. Jan Jaap Cannegieter (QATest 30-10-2013)

27. Scoping techniques
29

28. PRIMA
30

29. KANO
31

30. Story Decomposition
32

31. Story Mapping
33

32. Getting a grip on the project
34

33. Kanban
35

34. 36
Release Charts

35. Subway mapping
37
4 5
6
1 3
7 8 9
11 12
3.Credit
m
anagem
ent
ensuresthat
only
paid
goods
are
delivered
4.Usercan
accesssite
and
create
account
5.ProductDB
iscorrectly
M
igrated
and
usercan
add
selected
productsto
shopping
basket
6.Usercan
select
and
payproduct
8.Orderscan
be
processed
7.Ordersare
handled
to
back
office
11.FrontOffice
ordersare
processed:Picking,boxing
and
delivery
QGQG
1.Paym
entscan
be
m
ade
12
Pilot
11.Allthree
chainsare
integrated.Reallive
test
2
2.Paym
entsare
processed
on
financialdept.
15July
1Aug.
15Aug.
1Sept.
15Sept.
10
To be done (on me)
In progress (on me)
In progress (cri cal)
Done
Order processing
Front End Web shop
Payment
Delivery
In progress (delayed)
24 July 2013
6a
Project X
Subway map
Date: <Date >
By: <Name>
6a.User
getstrackand
trace
no
fica
ons

36. Business Benefit (MFF)
38

37. Lets do it a little different, this time
Facilitation Methods
39

38. Facilitation methods
Standup meetings
Mind map
Brown paper session
Sorting and Prioritizing
Process simulation
Gaming
Role playing
Demo
Interview techniques
40

39. Improvement techniques
41

40. Value Stream Map
42

41. Service Virtualisation
43
Assume a Process within a system that requires
interaction with other systems.
43
Step 1 Step 2 Step 3 Step 4
Ext
Syste
m
Ext
Syste
m
Ext
Syste
m
Considerations that
define the waste on the
interface:
• How often used
• Error proneness of
the interface
• Delay in processing
• Manual effort on the
interface
• Cost for processing
• Ability to test rainy
scenarios’
• Easy of investigating
errors
• Support issues
• High risk due to not
testing at all or error
situations
1 = delay
(waste) per day
based on normal
usage (or
testing)
1 3
5

42. Business Capacity model
44

43. Persona’s
45

44. Persona’s
46

45. Test Design
Error Creation
Error Detecting
Focus
(Scope & Prio)
GRIP
(Planning&Control)
Test
Improvement
Facilitation
Methods

46. Draw-back
When showing one techniques,
people are are likely to state that
they missed another technique.
48

47. Test Design
Error Creation
Error Detecting
Focus
(Scope & Prio)
GRIP
(Planning&Control)
Test
Improvement
Facilitation
Methods
Root Cause
Analysis
techniques*
*Thanks to Jan van Moll

48. Test Design
Error Creation
Error Detecting
Focus
(Scope & Prio)
GRIP
(Planning&Control)
Test
Improvement
Facilitation
Methods
Root Cause
Analysis
techniques*
*Thanks to Jan van Moll

49. Wrap-up
51

50. Quick replay
52

51. 53

52. 54
More reading…

53. 55

54. SUCCESS !
Derk-Jan
Valori
Coltbaan 4a
3439 NG NIEUWEGEIN
The Netherlands
derkjandegrood@valori.nl
+31(0)651807878
@DerkJanDeGrood
http://djdegrood.wordpress.com
56
Slides:
http://www.slideshare.net/DerkJandeGrood/unpack-
your-toolkit-becoming-more-effective-with-the-right-
tools-and-techniques