Related Content
 |
Moving into a World of Conscious Quality Conscious quality is a quality effort that is independent, end-to-end, and stretches beyond the bounds of the core test team. If conscious quality is not adopted, we run the risk of losing the sanctity of our independence, impacting the quality of the product as well as our careers are testers. |
|
 |
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. |
|
 |
Stronger, Faster Quality with Simple, Focused Checks Imagine focusing on prioritized business requirements at the software layer closest to where those business items are implemented. Writing just one check—that is, a programmed verification—per business requirement makes for simple, focused checks, supporting stronger, faster quality around the team. |
|
 |
Building an Effective Lean Testing Strategy Lean testing strategies can help QA teams effectively mitigate wasted resources and ensure that they are giving each project the attention it deserves. Sanjay Zalavadia details some strategies QA teams should implement in order to create an effective lean testing practice for their operations. |
|
 |
What Are You Measuring? Many teams do single-point measurements in their projects. But that doesn't give you a good long-term picture. When you look at multiple-dimension measurements—especially trends over time—you learn more. You can take those trends into a retrospective to investigate how your team could work better. |
|
 |
The Lean Startup Methodology and Its Value for Testers Testers are rarely part of an entrepreneurial startup team, but are there lessons for them in the lean startup approach? Lee Copeland says yes. The basic idea behind lean startup is that companies should focus their time and resources more efficiently, and this concept surely can benefit testers. |
|
 |
The Word “Automation” Has Led Us Astray The misunderstanding that automation for software quality is just doing what humans do (i.e., manual testing), but faster and more often, causes business risk. Unless you’re very clear, the quality measure is incomplete. The word automation distracts from the real value: measuring quality. |
|
 |
Testing Nonfunctional Requirements in an Agile Lifecycle As organizations embrace agile, requirements become a challenge because they must be considered and validated in each (short) sprint. Ideally, nonfunctional requirements should be a continuous focus throughout the project. Here are some ways to better address NFRs in an agile development lifecycle. |
