The higher you climb in the organization, the less information you get: An executive might only see red, yellow, and green for a project. Any time different teams need to communicate complex information, there is bound to be some information loss, and maybe some information control. We just need to understand where and why that happens, and—hopefully—how we can mitigate it.
Testers and developers often have a strained relationship. Each side has a certain level of expectations as to what the other side should know and do, while there is little understanding of the constraints, conditions, and requirements that the other team has to work within. But it does not have to be this way. A little effort in giving more specific and helpful feedback can go a long way toward improving attitudes.
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.
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.
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.
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.
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.
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.
Testers tend to be innately curious creatures. Being curious and evaluating risks—that is what the testing job is about. Often it is the statement “I don’t know” that drives our curiosity in testing. Find out not only how to push past the fear of not knowing but how to embrace your curiosity.
Communication is at the heart of our profession. No matter how advanced our testing capabilities are, if we can’t convey our concerns in ways that connect with key members of the project team, our contribution is likely to be ignored. Because we act solely in an advisory capacity, rather...
Thomas McCoy, Australian Department of Social Services