The document provides a guide on agile testing using a whole-team approach, including an interactive domino-building activity to illustrate teamwork roles. It emphasizes the importance of testing throughout the development process and shares practical tips for effective collaboration and testing strategies. Additionally, it lists resources like books, blogs, and meetups for further exploration of agile testing concepts.

1. Agile
Testing
Whole-Team Approach

2. Standing survey
Stand up if you’d say yes to these questions...
Don’t be shy :)

3. Let’s Play Domino!
REQUIREMENT
1. Build a structure
that is at least 4
horizontally standing
domino blocks high.
2. Use all your blocks
3. Once you’re done with
each round, write
your time in the
flipchart sheet and
proceed to the next
round

4. Let’s Play Domino!
ROLES: In your teams, assign:
- 2 “testers”
- 1 timekeeper
- Everyone else are “builders”

5. Round # Time to “DONE”
1
2
3

6. Agile Manifesto
Agile mindset that should annihilate the older ones
TESTING
^

7. Testing throughout At the end
Preventing bugs Finding bugs
Testing understanding Checking functionality
Building the best system Breaking the system
Team responsibility Tester responsibility
-OVER-

8. Tips and Tricks
Some practices you can get started w ith right away

9. Questioning
* during team planning,
start with “WHY?”
* what ‘success’ looks like?
* clarify assumptions
Credit: https://pixabay.com/en/questions-puzzle-who-what-how-why-1328347/

10. Credit: BJ Edward Taduran and iEventify Team
Flows and Wireframes
* visualize “shared
understanding” with entire
team
* draw up system
relationships & interactions

11. Credit:Software Testing PH Meetup @ Venturespace / Titan Tech
Collaborative Mindmapping
* brainstorm and design
tests as a team
* visualize it with mind
maps or post-its
* focus on risks

12. Credit: Ecal Team @ Oxygen Ventures Australia
Desk Checking
* dev to demo in his local
* check it against
acceptance criteria
* soft-log the feedback

13. Credit: Jon Bach, “The Freedom Scale”
Exploratory Testing
* don’t pre-design tests as
if everything is certain
* reduce cost of
documentation to absolute
minimum

14. Credit: http://blog.agilistic.nl/8-useful-strategies-for-splitting-large-user-stories-and-a-cheatsheet/
Per-Item Testing
* make tasks as small as
possible, then ‘test early
and often’
* get rid of “environment
ownership”

15. Next steps
What you should do from today
(rather than sharing Facebook hoax or fake news site)

16. Credit: Five Monkeys uploaded by Goran Sijak https://www.youtube.com/watch?v=y-PvBo75PDo

17. Resources
Books - “More Agile Testing”, “Exploratory
Testing”, Growing Agile book series
Blogs & Tweets - Michael Bolton, James
Bach, Gojko Adzic, Ian Pestelos :)
Meetups - Agile Philippines and Software
Testing Philippines group in Facebook

18. Questions?
me@ianpestelos.com
@ianpestelos
/in/ianpestelos