The document discusses collaboration between developers and testers, highlighting methods like mob programming and strong-style pairing to improve quality. It emphasizes the importance of exploratory testing, unit testing, and effective communication in achieving better outcomes. The authors, Maaret Pyhäjärvi and Llewellyn Falco, encourage connections through social media for further discussion.

1. @maaretp
@LlewellynFalco

2. Developing a new feature

3. Developer

5. Tester

7. ?!?%#

8. Except…

9. A day of mobbing

10. * http://visible-quality.blogspot.fi/2015/09/my-first-full-day-of-mob-programming.html
That would’ve
been a nasty
one to find
later

11. Co-creation
vs.
Collaboration

12. Tales from Developer Tester
Collaboration
Maaret Pyhäjärvi & Llewellyn Falco

13. 1st session on unit testing
* http://visible-quality.blogspot.fi/2015/01/a-learning-journey-with-unit-tests-just.html

14. Strong Style Pairing
“For an idea to go from your head to
the computer it must go though
someone else’s hands”
*http://llewellynfalco.blogspot.fi/2014/06/llewellyns-strong-style-pairing.html

15. Farming vs. Hunting

16. “Look at me” Pairing

17. Why are we having issues?

18. How we became how we are

19. Exploratory Testing

20. Testing Excel

21. What Testing Gives Us
UnitTesting
ExploratoryTesting
SPEC
FEEDBACK
REGRESSION
GRANULARITY
GUIDANCE
UNDERSTANDING
SERENDIPITY
MODELSTesting as
artifact
creation
Testing as
performance

22. Why do this?
“It’s about getting the best (not the most)
out of everyone”

23. Quality

24. Quality

25. Quality
Some dev care about testing
Pairing & Mobbing
Remote desktop
More powerful unit tests
Some testers are great product owners
MindMaps are amazing
Skilled tester exist
Testers don’t
report
everything
Learning's:
Shortcuts & Cheats

26. Thank you.
@maaretp
@LlewellynFalco
(please connect with us through Twitter or LinkedIn)