requirements | TechWell

requirements

A list of requirements with checkmarks Testing the Requirements: A Guide to Requirements Analysis

Everyone knows testing requirements is important, and everyone says they do it, but it seems like no one knows exactly how. The best way to solve this problem is to introduce a requirements analysis stage that has to be done before coding starts. No one knows a product as well as a tester who works with it every day!

Evgeny Tkachenko's picture
Evgeny Tkachenko
Illustration of minimum viable product with cars Interface Grief: Is It Agile, or Just Bad Software Engineering?

There are people who will use "being agile" to justify software engineering practices that could be perceived as lazy or even bad. The specifications are going to change, they say, so it would be a waste to engineer more to begin with than the minimum viable product. What's expediency and what's just poor practice?

Payson Hall's picture
Payson Hall
User stories Use Continuous Backlog Grooming to Refine Agile Requirements

Continuous backlog grooming means systematically refining your user stories: breaking up larger stories, obtaining detailed requirements, writing the requirements in terms of acceptance criteria and acceptance tests, and sharing and refining these details with the team. Acceptance test-driven development can help.

Susan Brockley's picture
Susan Brockley
Acceleration Build the Right Things and Build Them Fast: Accelerate the Continuous Delivery Pipeline

When most people think about continuous delivery, they think of improving the build-test-deploy-operate cycle. They don’t think about how to improve the intake process. Ensuring that quality is built into the application—not tested for after the fact—is the key to achieving accelerated continuous delivery.

Alex Martins's picture
Alex Martins
Why Is Estimating Software Testing Time So Difficult?

Management loves to ask testers to estimate how long their efforts will take. But so many important factors elude measurement that it makes it difficult to predict. If you need to explain why estimation is so tough, here are nine factors that significantly influence our ability to estimate testing time.

Lee Copeland's picture
Lee Copeland
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?

Mukesh Sharma's picture
Mukesh Sharma
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.

Josiah Renaudin's picture
Josiah Renaudin
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.

Payson Hall's picture
Payson Hall