This article discusses how the relationship among the five principal metrics of the software process can often be expresses through a Rayleigh curve.
This article discusses multiple applications based on only four measured metrics: size (function), effort, time, and defect rate. From these metrics, we can manage a project.
This article discusses team size and the effectiveness of smaller groups in the work place.
This article discusses how metrics can be used to understand where you've been and how effective your organization can be.
This article discusses the importance of feasibility and how metrics interact with this concept of feasibility.
This article discusses the software cost estimation problem and how metrics and acceptance can solve it.
This article discusses how SLIM can be used to prepare for and assess the costs the year 2000 may bring.
“The only way to increase product quality and reduce cost while concurrently improving product development speed is to fundamentally change the development process itself.”
Christopher Meyer 1
This article discusses how, in software development, metrics can provide managers some assurance that the development can be conducted within bounds of cost, schedule, and reliability.
This article discusses how projects can now be estimated and bid with reasonable precision, allowing for a fact-based position in negotiations.