Best Practices for Software measurement and Metrics
Critical Software Practices: #3: Use Metrics to Manage - The SPMN was established in 1992 by the Assistant Secretary of the Navy to identify proven industry and government software best practices and convey these practices to managers of large-scale DoD system acquisition programs. The SPMN 16 Critical Software PracticesTM specifically address underlying cost and schedule drivers that have caused many software intensive systems to be delivered over budget, behind schedule and with significant performance shortfalls.
Practice Number 3 is Use Metrics to Manage. Details can be found on the SPMN web site listed below.
SPMN Critical Software Practices: #4: Track Earned Value - The SPMN was established in 1992 by the Assistant Secretary of the Navy to identify proven industry and government software best practices and convey these practices to managers of large-scale DoD system acquisition programs. The SPMN 16 Critical Software PracticesTM specifically address underlying cost and schedule drivers that have caused many software intensive systems to be delivered over budget, behind schedule and with significant performance shortfalls.
Practice Number 4 is Track Earned Value. Details can be found on the SPMN web site listed below.