Requirements volatility (percentage of requirements changes)
Number of requirements by type or status (defined, reviewed, approved, and implemented)
Cumulative number of changes to the allocated requirements, including total number of changes proposed, open , approved, and incorporated into the system baseline
Number of change requests per month, compared to the original number of requirements for the project
Amount of time spent, effort spent, cost of implementing change requests
Number and size of change requests after the Requirements phase is completed
Cost of implementing a change request
Number of change requests versus the total number of change requests during the life of the project
Number of change requests accepted but not implemented
Number of requirements (changes and additions to the baseline)
Completion of milestones for the project planning activities compared to the plan (estimates versus actuals)
Work completed, effort and funds expended in the project planning activities compared to the plan
Number of revisions to the project plans
Cost, schedule, and effort variance per plan revision
Replanning effort due to change requests
Effort expended over time to manage the project compared to the plan
Frequency, causes, and magnitude of the replanning effort
Effort and other resources expended in performing monitoring and oversight activities
Change activity for the project plan, which includes changes to size estimates of the work products, cost/resource estimates, and schedule
Number of open and closed corrective actions or action items
Project milestone dates (planned versus actual)
Number of project milestone dates made on time
Number and types of reviews performed
Schedule, budget, and size variance between planned and actual reviews
Comparison of actuals versus estimates for all planning and tracking items
Number of projects using progress and performance measures
Number of measurement objectives addressed
Cost of the COTS (commercial off-the-shelf) products
Cost and effort to incorporate the COTS products into the project
Number of changes made to the supplier requirements
Cost and schedule variance per supplier agreement
Costs of the activities for managing the contract compared to the plan
Actual delivery dates for contracted products compared to the plan
Actual dates of prime contractor deliveries to the subcontractor compared to the plan
Number of on-time deliveries from the vendor, compared with the contract
Number and severity of errors found after delivery
Number of exceptions to the contract to ensure schedule adherence
Number of quality audits compared to the plan
Number of Senior Management reviews to ensure adherence to budget and schedule versus the plan
Number of contract violations by supplier or vendor
Completions of milestones for the QA activities compared to the plan
Work completed, effort expended in the QA activities compared to the plan
Number of product audits and activity reviews compared to the plan
Number of process audits and activities versus those planned
Number of defects per release and/or build
Amount of time/effort spent in rework
Amount of QA time/effort spent in each phase of the life cycle
Number of reviews and audits versus number of defects found
Total number of defects found in internal reviews and testing versus those found by the customer or end user after delivery
Number of defects found in each phase of the life cycle
Number of defects injected during each phase of the life cycle
Number of noncompliances written versus the number resolved
Number of noncompliances elevated to senior management
Complexity of module or component (McCabe, McClure, and Halstead metrics)
Number of change requests or change board requests processed per unit of time
Completions of milestones for the CM activities compared to the plan
Work completed, effort expended, and funds expended in the CM activities
Number of changes to configuration items
Number of configuration audits conducted
Number of fixes returned as "Not Yet Fixed"
Number of fixes returned as "Could Not Reproduce Error"
Number of violations of CM procedures ( noncompliance found in audits)
Number of outstanding problem reports versus rate of repair
Number of times changes are overwritten by someone else (or number of times people have the wrong initial version or baseline)
Number of engineering change proposals proposed, approved, rejected, implemented
Number of changes by category to code source, and to supporting documentation
Number of changes by category, type, and severity
Source lines of code stored in libraries placed under configuration control