Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Metrics"
Jump to navigation
Jump to search
Line 44: | Line 44: | ||
=== Bug Metrics === | === Bug Metrics === | ||
Bug metrics are used to ensure the quality of the application by keeping track of the number of bugs that occur during development. | Bug metrics are used to ensure the quality of the application by keeping track of the number of bugs that occur during development. | ||
+ | <br> | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AurhQPwcmXKIdGZJVm13ckpNRE1DdFBRMkxNcFBfVFE#gid=0 Bug metrics document] | ||
+ | |||
[[Image:Bug_score.png|center|750px]] | [[Image:Bug_score.png|center|750px]] | ||
Line 53: | Line 56: | ||
− | + | ||
=== Velocity Metrics === | === Velocity Metrics === | ||
Velocity metrics ensure that our project tasks are completed within the schedule timeframe so that the project deadline can be met. The score is retrieved from Pivotal Tracker. | Velocity metrics ensure that our project tasks are completed within the schedule timeframe so that the project deadline can be met. The score is retrieved from Pivotal Tracker. | ||
− | + | <br> | |
+ | [https://docs.google.com/spreadsheet/ccc?key=0AurhQPwcmXKIdGZJVm13ckpNRE1DdFBRMkxNcFBfVFE#gid=1 Velocity metrics document] | ||
[[Image:MOOT_schedule_metric.png|center|750px]] | [[Image:MOOT_schedule_metric.png|center|750px]] |
Revision as of 01:26, 16 August 2012
Project Schedule | Methodology | Metrics | Risk Management | Minutes Repository |
Bug Metrics
Bug metrics are used to ensure the quality of the application by keeping track of the number of bugs that occur during development.
Bug metrics document
Velocity Metrics
Velocity metrics ensure that our project tasks are completed within the schedule timeframe so that the project deadline can be met. The score is retrieved from Pivotal Tracker.
Velocity metrics document