Have you said to yourself “I’m not technical enough to join that discussion”, or perhaps said to someone else “This will be too technical for you – don’t worry about joining.”

It is these types of biases that make team members miss important nuances that can lead to a better implementation of a story or feature. Meetings to talk about system architecture, code design, data structure design, the technical implementation of a new feature, or other topics that are seen as “technical”, may exclude “non-technical” team members. That means leaving out people with diverse perspectives who may have ideas and ask questions nobody else would think of. Janet shares tips on how to make this type of conversation happen and include all the right people – including the ones that some perceive to not be “technical enough”. In this workshop, you’ll have the opportunity to try these techniques out yourself. Hands on exercises will allow you to practice so that you can contribute to a technical discussion or enable “non-technical” team members to contribute effectively.

Learning Objectives:
– Identify good ways to transfer skills across roles
– Become familiar with the tools and terminology used by other roles so you can collaborate comfortably
– Promote the whole-team approach to building a quality culture

——————————————-
About Janet
——————————————-
Co-founder and Master Trainer @ Agile Testing Fellowship
Provide agile consulting, training and coaching for agile teams, with specialties in agile testing and process consulting.
More than twenty years experience in software development. Over fourteen of those spent helping teams transition to an agile software development environment, specializing in helping testers and business understand their role as part of the ‘whole team approach’.
I bring a strong technical background balanced with a business perspective.
Specialties: Agile methodologies in software development, process improvement, testing.

https://www.linkedin.com/in/janetgregory/
https://twitter.com/janetgregoryca