This article presents approaches to estimate and manage more accurately the integration and test efforts.

This article presents an approach in which organisations achieve high performance without writing any more processes. Instead, they use processes that already exist, they measure key attributes, analyse them regularly and improve them in a systematic way.

This article explains how to improve testing efficiency with risk evaluation.

This article describes a practical tool to evaluate a number of critical factors, which determine the success or failure of (Software) Process Improvement programs.

This article presents a brief overview of software measurement. It describes why measurement is important, what you should measure, and some techniques for creating a measurement culture in your organization. A number of metrics that are appropriate for individuals, development teams, and software organizations to collect are suggested, along with several tips for making your metrics program succeed.

Software measurement is hard! This article describes 10 traps that can threaten the success of a metrics program. Symptoms of each trap, and suggested strategies for controlling it, are presented

For large projects, automated estimates are more successful than manual estimates in terms of accuracy and usefulness. In descending order, the costs of large projects include defect removal, production of paper documents, coding, project management, and dealing with new requirements that appear during the development cycle. In addition, successful estimates for large projects must be adjusted to match specific development processes, to match the experience of the development team, and to match the results of the programming languages and tool sets that are to be utilized. Simple manual estimates cannot encompass all of the adjustments associated with large projects.

A goal-driven method for developing and maintaining a meaningful metrics program that is based on three levels, Goals, Questions and Metrics. The approach uses metrics to improve the software development process (and its resulting software products) while maintaining alignment with organization business and technical goals.

This article answers basic questions about software maintenance for a single organization and discusses some of the decisions made based on the answers. These examples form a useful basis for other software maintenance managers to make better decisions in the day-to-day interactions that occur on their programs.

This report defines key factors to consider in taking an incremental approach to fielding a product line. An organization building a business case can apply these factors to show that product line investment can result in product development savings. The example presented here shows a net savings of almost $180 million in projects that would have cost about $600 million under traditional development approaches.