Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Metrics"
Jump to navigation
Jump to search
Line 47: | Line 47: | ||
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> | <br> | ||
− | [https://docs.google.com/spreadsheet/ccc?key=0AurhQPwcmXKIdGZJVm13ckpNRE1DdFBRMkxNcFBfVFE#gid=0 Bug metrics document] | + | Click to see the details of our bug log: [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]] |
Revision as of 23:56, 22 September 2012
Project Schedule | Methodology | Schedule & Bug Metrics | Gender Recognition 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.
Click to see the details of our bug log: 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.
Iteration-Velocity Progress | |||||||
Iteration No. |
Start Date |
End Date |
No. of Days |
Points | Baseline Velocity | Score (Pts - Velocity) |
Remarks |
1 | 17/08/2012 | 01/09/2012 | 14 | 23 | 0 | 23 | N.A. |
2 | 03/09/2012 | 08/09/2012 | 5 | 10 | 23 | -13 | *length of iteration 2 is half of iteration 1 *difficulties in implementing neural network |