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.
When it comes to what testers should focus on, people always say you have to think like a user. Aleksis Tulonen used to think he was good at doing that—until he started actually sitting next to his applications' users. Then he thought of all kinds of questions that testers should consider more often. He discusses what you can learn from your users.
In short, redistributed testing is a shift in the emphasis and responsibility for testing. Testers are reassigned to work closer to the business with users or business analysts or are embedded in the development team.By being involved in story and scenario writing, the testers help to refine requirements and improve their quality. How could your systems benefit from redistributed testing?
Naomi Karten shares how to ask the questions that ensure you and your customer are on the same page. Her tips include: 1) guard against conflicting interpretations; 2) don't jump to conclusions; 3) gather feedback early and often; 4) examine your rules for commenting; 5) conduct congruent questioning; and 6) find out what's important to your customers.
In this interview, Neeraj Tripathi, vice president of Global QA at Infor, goes over the principles of effective software quality management. He explains how to measure customer satisfaction and how active QA involvement eliminates defects early and shifts quality left.