quality assurance
 |
The Tester as Product Owner A lot of the bugs we find were never thought through in the first place. Many of these situations are preventable, yet instead of prevention, we get the tester playing the role of the product owner—and playing it late. Why is it that we never have time to do it right, but we always have time to do it over? |
|
 |
The Ethical Responsibility of Defect Severity Classification When dealing with defect classification, it's important to not blindly adhere to the criteria without consideration for real business or human implications. If your software does safety-critical work, do the defect levels reflect that? Or could something go live with potentially disastrous consequences? |
|
 |
How the Right Tools Can Help You Overcome Common Agile Pain Points Agile is a major undertaking for any business as it requires significant changes, and there are a number of issues that teams can experience along the way. Sanjay Zalavadia looks at some common agile pain points and how the right tools can help organizations overcome these issues. |
|
 |
Quality in Quantity: How App Quality Is Now Everyone’s Responsibility Quality has increasingly become a responsibility for not just one single segment of the team, but the team as a whole. It’s important for each member of a team to have some hand in making sure that what’s being developed works as intended as it goes through each individual progression. |
|
 |
Google’s Magic Metric Google has a "magic metric" that determines where effort should be spent, based on the fact that the number of hits on every site with one of its ads is directly correlated to revenue. Most companies do not have a magic metric, so they search for a way to measure process. How can you change the conversation? |
|
 |
Improving Product Quality throughout the Software Development Lifecycle Good, efficient communication is an important asset to the team. With focused, pure, and structured data on product quality, including all of the self-documenting steps of a given check, it’s clearly known what’s working and what the verifications are. Matt Griscom shows how you can get this level of clarity. |
|
 |
Jelly Beans and Defect Classification: Different Strategies for Success When there’s a bowl of jelly beans, some people grab a few at random, but most of us have favorites. If you're crafty and have flexible standards, you can maximize consumption by adjusting your criteria as colors dwindle. Classifying defects should not be like choosing jelly beans; you need firm standards. |
|
 |
Handling a Check Failure in Test Automation What happens on your team when a check (what some call “automated test”) fails? Regression tests or checks that are effective toward managing quality risk must be capable of sending action items outside the test/QA team quickly. How do you provide fast, trustworthy quality communications from your team? |
