Software development teams think nothing about reusing code, but what about requirements? The benefits include faster delivery, lower development costs, consistency across and within applications, fewer defects, and reduced rework.

Testers and developers can be friends. In fact, on teams working at a breakneck pace to deliver software, they must be friendly enough to rely on each other. However, there are a few sure-fire ways to ruin that relationship before it begins—and potentially make testing both irrelevant and unwelcome. Marlena Compton lists seven such ways here, along with suggestions for avoiding disaster.

Analysts determine what needs to be created. Programmers create it. Testers find the holes in the work of both. That's one way to do it, but all three can collaborate to do these things better, and more easily, too.

A cast-in-concrete delivery date looms on your project’s horizon. You have precious little time remaining, and the development team keeps delivering incomplete builds of unstable code. Is this a "death march" project, or can the testing team actually do something useful, or perhaps even save the day?