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.

Web development may be distinguished from traditional software development by descriptive terms such as "slam it and jam it," "FAD--Frantic Application Development," or "Wild Web Developer." These phrases from Glass' column help us understand the new challenges faced by test and QA people who are assigned to Web projects. In this column, Glass identifies many of the new aspects of testing that come with the advent of Web software.