For any project, the big question is: "Is this software ready to release yet?" Explore how to answer that question with confidence, by learning how to define success and how to gain consensus on release criteria.

Johanna Rothman urges test managers to stop whining and deal with the "Not-Enough" problem. She concludes: "You have more capability to influence attitudes, behaviors, and actions in your organization than you know. If you feel like a second-class citizen, reframe the situation. Rethink your job and how you do it, and realize the importance of the contribution–finite, but powerful–you can make toward your organization's product quality."

Are you challenged with having to hire people when your budget is limited, time constraints are tight, and the testing effort is overwhelming? Many of us have faced these situations. In this article, Jack Cook shares some techniques that have proven effective in recruiting and retaining testers.

We're all looking for an effective "Distant Early Warning" line of testing: a procedure that will minimize integration bugs, reduce the risk of low quality by allowing bugs to be caught early, make it easier to debug, and improve the visibility of the status of the system under test. One practice that meets those needs is the "nightly"—essentially a daily build and sanity test of the product.