Tutorial J

Social Software Testing Approaches

Maaret Pyhäjärvi

13:30-17:00 CEST Tuesday 13th June

Cross-functional teams have team members with specialized in-depth skills. Collaboration between team members has a significant impact on the team’s ability to deliver value efficiently. Software teams are well aware of the need for their developers, testers, product owners, and other team members to collaborate.

Product backlog refinement, 3-amigos sessions and daily meetings create space for sharing planning of the work, but for much of the rest of the time, people are hunched over their own keyboards and screens, working on their own tasks. Even if developers work with each other during pair programming and code review sessions, testers often work on their own.

In this tutorial, we learn approaches involving a more social aspect that teams can adopt in order to work together and improve their testing, as well as work better with developers. We experience and learn about: Traditional and Strong-style pair testing-Ensemble testing and Ensemble Programming-Bug bash.  Why does the social way of doing the work make sense?

Software development is not about getting the most out of us, but the best out of us -avoiding the ping pong, creating ideas we would not generate alone, and sharpening our skills. We don’t know what we don’t know but can recognize it in the context of doing it.

In software development, those who learn the fastest do best. In addition to learning within the team, we can extend from learning within the team to the community: testing tours applying these approaches give you hands-on experiences working with others even in other companies.

This is a hands-on course, where we experience combinations of four social software testing approaches with three testing tasks: one we pair on, one we ensemble on, and one we do a bug bash on. You learn to successfully set up each of the activities, and recognize how to prepare, facilitate and summarize sessions for a good collaboration experience.