The Latest

Ever been in a situation where everybody on the design and development team thinks they agree on the requirements-until you try to design that first screen or page?

Many organizations institute testing and quality improvement initiatives focused on testers, developers, and software managers. One stakeholder often ignored in these efforts is the user-your customer.

Have you ever heard something like “This feature (system) doesn't look anything like what I expected and doesn't do what I want”-even though you were confident that you knew what your customers wanted?

In this jab at the traditional test lab approach to testing software and Web services, Ken Johnston explains the what, why, and how of the practices and processes for testing in production (TiP).

Nonfunctional requirements are an essential part of a holistic understanding of system requirements; yet many teams struggle with them.

We understand the vital importance of collaboration among team members. However, how can we deal with non-collaborators-people who won't work with us?

Business rules and data needs are essential ingredients for a balanced set of requirements and are vital for successful product delivery. When analyzing requirements, some teams focus on business rules at the expense of data.