requirements
 |
Validate Your Core Business Assumptions Early On Verifying whether a product is being built per specifications is only solving half of the problem. Validation is a very significant activity performed by testers to ensure that the final product is ready for consumption by users and answers an important question. Are we building the right product? |
|
 |
IoT Devices: Why Accessibility Should Be Your First Priority Just because something is new, shiny, and more fully featured doesn’t mean that everyone is going to want to use it. Even if your IoT-enabled smart grill is voice-activated, it still has to be both consistently functional and as easy to use as a regular grill. |
|
 |
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. |
|
 |
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 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. |
|
 |
Five Techniques for Creating Testable Requirements Documenting user requirements is always a challenging phase in software development, as there are no standard processes or notations. However, communication and facilitation skills can make this activity easier. Here are five techniques for converting user stories into testable requirements. |
