The Latest

The project plan is clear and the specifications are detailed. So why is the final product so different from what you expected? In this week's column, Nicole Auger brings a product manager's perspective on how features get changed or added during the development process. And she gives tips on how to get what you ordered, instead of a substitute.

In any test automation effort, there are "sweet spots," points of leverage where you get more for your automation efforts.

Test automation raises our hopes yet often frustrates and disappoints us. Although automation promises to deliver us from a tough situation, automating implemented tests can create as many problems as it solves.

Many of us have worked in test groups where we felt as if we didn't have enough time, staff, or computer resources to do the work. We may not even know precisely what we need to test.

Since the subjective aspects of software quality do not lend themselves to being put into numbers or graphs, they are often overlooked.

How often have you been asked the question, "When will system testing be completed?" without knowing the final scope of the functionality, when the system will be ready for testing, and what test resources are available.

Explore how SynQuest implemented an evolutionary three-stage process of forming high performance teams who integrate test and quality throughout the product development process.