Metrics

List and Parameters

The following metrics details will be captured for future releases:

Project Management Related Metrics

Metric

Formulae

Inference

Effort Variation reflects our capability to execute project ((Actual Effort - Estimated Effort) / Effort within available budget by Variation (Estimated Effort)) *100 comparing actual effort against estimated effort Schedule Variation reflects our ((Actual End Date - Planned End Date) capability of on-time delivery. Schedule / This metric gives the no. of days Variation (Planned End Date- Planned Start) ) * slipped against the planned 100 schedule Load Factor reflects how resource utilization is there in Load Factor Actual Effort / Effort Available the project. It compares actual effort against allocated effort

Requirement Related Metrics Metric Formulae Inference This is used to measure the changes that are coming in (compared to the original requirements decided at the start of the project) during the course of the project This gives indication on effectiveness of the requirements elicitation process. Here the missed requirements are those that were missed by the Project team during Requirements Elicitation process

(Total number of Original Requirements + Requirement Cumulative number of requirements Stability changed / added / deleted) / Index (Total number of Original Requirements

Requirements (No. of Missed Requirements / Total Leakage no. of initial requirements) * 100 Index

Test Design Related Metrics Metric Formulae Inference This metric reflects the total no. of test case points that could be prepared per person days of effort

Test Case Total no. of test case points / Effort Preparation spent for test case preparation Productivity Test Case delivered defect density

(Total Number of test case review To determine the effectiveness defects reported by customer/Total no. of our test case review and also of test cases delivered) our test case quality

Test Execution Related Metrics Metric Test Execution Coverage Formulae Inference This metrics is useful to measure the number of test case executed against the plan This metric is useful to measure the percentage of test cases successfully executed To determine the effectiveness of testing Defined as ratio of defects per test cases To determine the effectiveness of testing and also the delivery capability This metrics shows the efficiency of detecting defects by Testing before delivering to customer

Total Number of test cases or scripts executed / Total Number of test cases or scripts planned to execute) * 100 (Total Number of test cases or scripts Percentage of executed and passed / Total Number test cases of test cases or scripts Executed) * passed 100 (Total no. of cognizant reported % Defect Defects rejected by customer /Total Rejection no. of Defects Reported by cognizant) * 100 Total number of defects found in Error Discovery application /Number of test cases or scripts executed Rate Residual (Total number of Post-Production Defect Defects)) / (Total Actual Effort) Density ((Total number of System testing Test Effectiveness defects - Total number of defects rejected) / % (Total number of defects + Total number of defects found during User Acceptance Testing)) * 100 %Rework (Total Rework Effort (across all Stages)) / (Actual Effort expended for Effort the project)*100

To determine the effectiveness of testing