Abstract/Description

OK, we lied, there is never a right way to say “yes” to that question. However, as testers (and most roles), there are times when we have to communicate negative or difficult messages to others. It’s vital that we can learn to do this without generating emotional situations, destroying people’s trust or causing conflict.

More generally though, have you ever said something that someone has completely misinterpreted? Most of us work in teams, and even though communication seems simple and is something we do every day, a lot of our communication is misunderstood, which can lead to developing the wrong thing! This is further complicated for teams that aren't co-located.

Learning ways to communicate helps us to understand people and situations better, which helps to create an environment where problem solving and idea creation can thrive. A team which has good, open communication can collaborate towards the right end product. Being a good communicator and being able to resolve any differences means you build the trust and respect of your team and business stakeholders that you need to be able to do your job well.
This session is suitable for testers of any experience level, as well as team members in any discipline who are interested in improving tester-coder communication and collaboration. The session will:
-look at all the ways we communicate daily, then focus on the key communications of a test engineer and ways to do this well.
-look at the information testing can provide and ways to communicate that information so that it is received well.
-identify one of the key skills a team needs, which is even more key as a tester helping to deliver quality.
-look at ways to build communication skills within common meetings within the agile process.
-identify key ways to maintain good communication within distributed teams.

Additional Resources

About the Speaker(s)

Emma comes with a degree in Computer Science many moons ago and chose to work as a test engineer, starting out as a compiler tester in the semi conductor chip industry. During this time she became familiar with both hardware and software and used many languages (ARM, C PHP etc) to develop and enhance automated testing against a suite of tools and enable developers to be able to initiate their own builds and determine the status of these and allow them to investigate build issues early. This good grounding in the develop lifecycle and the varied development activities from what is now called DevSys, develop build and test through to release was invaluable to the rest of her career. She has continued this career path under different job titles and in different methodologies and varied languages but always believing that it is important to consider the whole development cycle from conception through to release, support and maintenance. This led over the last twelve years to a feeling of affinity with the agile development methodology. She has been actively involved in training and coaching internally throughout her career and but stepped out of her comfort zone to reach a wider audience within the community. Being part of the BBST training team, speaking at conferences and running workshops.

Lisa Crispin is the co-author, with Janet Gregory, of More Agile Testing: Learning Journeys for the Whole Team (2014), and Agile Testing: A Practical Guide for Testers and Agile Teams (2009). Lisa was voted by her peers as the Most Influential Agile Testing Professional Person in 2012. Please visit www.lisacrispin.com and www.agiletester.ca for more.