Development Agile Test & Quality Assurance Project Management Requirements
CM & ALM Devops Cloud Mobile People & Teams

By Topic

Requirements

Requirements and Business Analysis Stories
View from above of five coworkers fist-bumping over their computers 4 Ways to Increase Software Quality and Decrease Test Time

Software testers are continually under pressure to test faster without sacrificing quality. By taking the perspective that quality is the responsibility of the entire team, not just the testers, shorter test cycles with higher quality software are possible. Here are four ways the whole team can improve releases.

Richard Estra's picture
Richard Estra
Cartoon showing a customer's request for a tree swing A Tester’s Role in Requirements Exploration

Agile is supposed to get people to talk to each other in real time. However, many teams still lack a shared understanding of what they are going to build, even as they start coding. As testers, we can explore feature specifications early, contributing to successful and timely delivery through defined requirements.

Janet Gregory's picture
Janet Gregory
Sheet of paper outlining software requirements Improving Requirements with Preemptive Testing

Most product defects are created during requirements definition. To significantly reduce and prevent requirements problems, consider making their management your software testers' responsibility. They can identify requirements defects as they are being developed, as well as work out mitigations for their root causes.

David Gelperin's picture
David Gelperin
group at table The World Has Product Ideas—and So Can You

From where do organizations—both big and small—get product ideas? Most often, pioneers and revolution makers have ideas that are homegrown, but today the market is such that the world has ideas. Our industry has plenty of patterns, trends, and ideas to work on and augment.

Mukesh Sharma's picture
Mukesh Sharma
accessibility Are You Reluctant to Venture into Accessibility Engineering?

Organizations are beginning to give a lot of attention and importance to accessibility engineering as part of their usability efforts; however, this has not translated into implementation strategies that have reached the market. Why is there a reluctance to venture into full-fledged accessibility engineering?

Mukesh Sharma's picture
Mukesh Sharma
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
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
stealth bomber The Balance between Being Stealth and Being Public during Product Development

While end user data protection is important from a business to customer perspective, businesses themselves have their share of data protection problems. Organizations need to find the balance between being in a stealth mode and being too public during product development.

Mukesh Sharma's picture
Mukesh Sharma