communication

Articles

Testing team standing around a computer and smiling 3 Methods for Better Communication and More Effective Testing

Successful delivery of software requires the entire team, so it’s imperative that everyone choose their words carefully so they convey what they really mean, are sensitive to others’ feelings, and consider all aspects of a problem. Here are three questions to remember when communicating about your software testing projects to ensure you’re considering the power of words.

Ajay Balamurugadas's picture Ajay Balamurugadas
Hand holding black rotary telephone When DevOps Gets Lost in Translation

The waterfall method of developing software is a bunch of translation activities: The design is a translation of the requirements into the language of architecture, the code is another, and a formal test process is a third. And with each translation, there’s the opportunity to introduce error. When your DevOps team is isolated, it creates another handoff, and another point of failure.

Matthew Heusser's picture Matthew Heusser
Marcia Buzzella Improving Communication and Social Skills: An Interview with Marcia Buzzella
Video

Marcia Buzzella, an independent leadership consultant and strengths coach, discusses the importance of communication and social skills in a business atmosphere. She offers advice on tools to recognize your weaknesses in those areas and how to work toward improving your effectiveness.

Jennifer Bonine's picture Jennifer Bonine
Marcia Buzzella Why Testers, Developers, and Managers Need Better Communication: An Interview with Marcia Buzzella
Video

In this interview, Marcia Buzzella, a leadership consultant and strengths coach, explains how each member of a software development team can better communicate with one another, and why testers need to understand how what they’re saying is being perceived.

Jennifer Bonine's picture Jennifer Bonine
Jess Agile Improv Agile, Improv, and Learning How to Fail: An Interview with Jessie Shternshus
Podcast

In this interview, Jessie Shternshus, the owner and founder of The Improv Effect, explains the similarities between agile development and improvisation. She details how, in both cases, team members need to learn how to support each other, build on work, and be comfortable with failure.

Josiah Renaudin's picture Josiah Renaudin
Janet Gregory Key Skills Modern Testers Need: An Interview with Janet Gregory

In this interview, Janet Gregory, an agile testing coach and process consultant with DragonFire, explains what skills testers need to succeed in today's industry. She talks about how the testing role has changed, what communication skills testers need, and the importance of trying new things.

Josiah Renaudin's picture Josiah Renaudin
Selena Delesie Leadership Lessons to Bolster Your Software Team: An Interview with Selena Delesie
Video

In this interview, visionary speaker Selena Delesie explains how successful teams embrace specific principles, including listening deeply, believing people truly matter, having an addiction to learning, serving others, flowing through change, moving through fear, and following joy.

Jennifer Bonine's picture Jennifer Bonine
TJ Usiyan How Ideas and Assumptions Impact Applications: An Interview with TJ Usiyan
Podcast

In this interview, TJ Usiyan, an instructor with Iron Yard, talks about whether development and testing teams need to be on the same page. He also explains how subjectivity influences our systems and applications and why teams overlook subjectivity.

Josiah Renaudin's picture Josiah Renaudin
labels Semantics and the Risk of Labels in Software Testing

All industries have their own jargon practitioners use to communicate. Software testing surely has terminology most testers are familiar with and use to label artifacts frequently involved in their work. The problem becomes when testers hold too tightly to these labels, forgetting that the things they signify are what truly matters. It's important to remain flexible.

Jeremy Carey-Dressler's picture Jeremy Carey-Dressler
man guessing Don’t Guess Your Tests—Strive for Complete Requirements

Many teams struggle with test creation due to miscommunication or a lack of requirements, testers not being present during design phases or discussions, a shortage of time, or incomplete information. But that doesn’t mean you should turn to guesswork. Your tests will suffer in quality and completeness. We must always strive to get the desired requirements.

Nishi Grover's picture Nishi Grover

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.