Metrics and Measurements
Measurements:
- Milestone due dates
- Milestone completion dates
- Estimated time for task completion
- Time for task completion
- Time spent working
- Number of defects
- Number of test cases
- Test cases passed
- Classification of test cases
- Product response time
- Number of requirements
- Line of code in thousands
- Number of Tasks Todo
- Number of Tasks In Progress
- Number of Tasks Completed
Metrics
- Progress Metrics
- Milestone Completion
Shows number of days the project is ahead/behind schedule, based on planned dates for reaching milestones. Target dates are identified and actual dates for reaching each milestone are tracked.
- Measurements Used:
- Milestone due dates
- Milestone completion dates
- Cumulative Flow
- Shows the number of tasks in each state (Todo, In Progress, Completed)
- The relative flow of tasks should not spike - Too many new Todos is a sign we did not properly plan or overscoped the current iteration
- Milestone Completion
- Effort metrics
- These metrics are used for keeping track of hours spent.
- Comparison of planned versus actual effort for each activity. Effort on activity is tracked using time.
- Effort by type of activity: Classify effort based on activity type: requirements, design, implementation, coordination, documentation, customer interaction etc. Useful to identify where allocated time is going, so that we can try to improve efficiency in that area.
- Measurements used:
- Estimated time for task completion
- Time for task completion
- Estimation Accuracy, E% =(|TEstimate -TFinal|)/(TEstimate) *100
- Activity metrics
- Test metrics
- Number of test cases per requirement
- Percent of tests passed successfully
- Test metrics
Version | Date | Comment |
---|---|---|
Current Version (v. 3) | May 13, 2016 17:49 | IAN SALITRYNSKI (RIT Student) |
v. 2 | Feb 09, 2016 22:14 | IAN SALITRYNSKI (RIT Student) |
v. 1 | Feb 08, 2016 19:12 | IAN SALITRYNSKI (RIT Student) |