This paper discusses issues that have proven to successfully assemble responsive testing teams. If done properly, the team becomes a value added extension to the quality process. The issues discussed are not all the issues by any means. Nor are the proposed methods of dealing with these issues the only way to do so.

Rapidly changing application code and Web content can be a challenge for any eBusiness to manage. Requests from partners, customers, suppliers, and development teams must be tracked and implemented in an orderly way, with strong auditability. At stake is the quality of eBusiness applications, the accuracy of Web content and the ability to deliver both in a timely manner. This paper talks about how to manage the entire development lifecycle.

To survive, the Test Manager has to demonstrate the effectiveness of the Testing Process. The evidence to show this is required to be more than software defect metrics - how many raised, how many outstanding/fixed by severity and urgency etc. It needs to be comprehensive measurement of the code being tested and of the testing service provided to test it.

Many of us would like a precise answer to the question: "What's the correct staffing ratio for developers to testers in my product organization?" Usually, though, the only answer is "It depends." Your answer depends on your situation: the kind of project you're working on,
your schedule constraints, the culture you work in, and the quality expectations for the product. This paper discusses the thought process involved in deciding on your correct staffing ratios.