Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Metrics"
(11 intermediate revisions by 3 users not shown) | |||
Line 31: | Line 31: | ||
| style="font-size:90%; text-align:center;" width="10%" |[[ IS480 Team wiki: 2012T1 M.O.O.T/Project Management|<font color="#000000">Project Schedule</font>]] | | style="font-size:90%; text-align:center;" width="10%" |[[ IS480 Team wiki: 2012T1 M.O.O.T/Project Management|<font color="#000000">Project Schedule</font>]] | ||
− | |||
− | |||
| style="font-size:90%; text-align:center; background-color:#9400D3;" width="10%" |[[ IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Metrics|<font color="#ffffff"><b>Schedule & Bug Metrics</b></font>]] | | style="font-size:90%; text-align:center; background-color:#9400D3;" width="10%" |[[ IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Metrics|<font color="#ffffff"><b>Schedule & Bug Metrics</b></font>]] | ||
Line 55: | Line 53: | ||
− | [[Image: | + | [[Image:MOOT_Bug_metric.png|center|750px]] |
+ | [[Image:MOOTbugmetrics.png|center|750px]] | ||
+ | For iteration 2, we found two bugs. One bug was solved within the day itself, while the other bug which was found near the end of the iteration was particularly challenging and had to be brought over to the next iteration for it to be solved. Thus the net bug score for iteration 2 was 3 since the bug was not resolved by that iteration yet. Though the team met several bugs during iteration 3, the team managed to solve all bugs by the end of the iteration, resulting in a net bug score of 0. The same goes for the next few iterations. Fortunately, the team was able to solve all bugs within their respective iterations, hence there was no need to push the solving of bugs to the next iteration nor was there a need to consider dropping any functionality due to the inability to solve the bug. | ||
=== 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, and as the name suggests, measures velocity. Velocity is a measurement of how fast team completes stories (tasks), expressed in the number of points completed per iteration (every two weeks on average). It is believed to be better as it is not calculated based on wishful due dates, but on assigned point values. Pivotal Tracker calculates velocity by averaging the number of points completed over the past few iterations. Hence, based on existing pattern forming the average, the same number of points are taken for upcoming iteration - the past predicts the future. |
<br> | <br> | ||
Line 100: | Line 100: | ||
| style="background: #2DAF7E; text-align: center;" valign="top" | 18 | | style="background: #2DAF7E; text-align: center;" valign="top" | 18 | ||
| style="background: #FFFEF5; text-align: center;" valign="top" | | | style="background: #FFFEF5; text-align: center;" valign="top" | | ||
+ | |- | ||
+ | | style="background: #FFFEF5; color: #000000; font-weight: bold; text-align: center; width: 10%;" valign="top" | 4 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 24/09/2012 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 05/10/2012 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 12 | ||
+ | | style="background: #2DAF7E; text-align: center;" valign="top" | 17 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | | ||
+ | |- | ||
+ | | style="background: #FFFEF5; color: #000000; font-weight: bold; text-align: center; width: 10%;" valign="top" | 5 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 08/10/2012 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 19/10/2012 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 12 | ||
+ | | style="background: #2DAF7E; text-align: center;" valign="top" | 17 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | | ||
+ | |- | ||
+ | | style="background: #FFFEF5; color: #000000; font-weight: bold; text-align: center; width: 10%;" valign="top" | 6 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 22/10/2012 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 03/11/2012 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 12 | ||
+ | | style="background: #FF4744; text-align: center;" valign="top" | 14 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | | ||
+ | Slight delay due to time spent in securing site and logistics preparation for UT at Plaza Singapura | ||
+ | |- | ||
+ | | style="background: #FFFEF5; color: #000000; font-weight: bold; text-align: center; width: 10%;" valign="top" | 7 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 05/10/2012 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 19/11/2012 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | 14 | ||
+ | | style="background: #2DAF7E; text-align: center;" valign="top" | 17 | ||
+ | | style="background: #FFFEF5; text-align: center;" valign="top" | | ||
+ | |- | ||
|} | |} | ||
Latest revision as of 10:57, 2 December 2012
Project Schedule | 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
For iteration 2, we found two bugs. One bug was solved within the day itself, while the other bug which was found near the end of the iteration was particularly challenging and had to be brought over to the next iteration for it to be solved. Thus the net bug score for iteration 2 was 3 since the bug was not resolved by that iteration yet. Though the team met several bugs during iteration 3, the team managed to solve all bugs by the end of the iteration, resulting in a net bug score of 0. The same goes for the next few iterations. Fortunately, the team was able to solve all bugs within their respective iterations, hence there was no need to push the solving of bugs to the next iteration nor was there a need to consider dropping any functionality due to the inability to solve the bug.
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, and as the name suggests, measures velocity. Velocity is a measurement of how fast team completes stories (tasks), expressed in the number of points completed per iteration (every two weeks on average). It is believed to be better as it is not calculated based on wishful due dates, but on assigned point values. Pivotal Tracker calculates velocity by averaging the number of points completed over the past few iterations. Hence, based on existing pattern forming the average, the same number of points are taken for upcoming iteration - the past predicts the future.
Iteration-Velocity Progress | |||||
Iteration No. |
Start Date |
End Date |
No. of Days |
Velocity | Remarks |
1 | 17/08/2012 | 01/09/2012 | 14 | 23 | N.A. |
2 | 03/09/2012 | 08/09/2012 | 5 | 10 | *length of iteration 2 is half of iteration 1 *difficulties in implementing neural network |
3 | 10/09/2012 | 22/09/2012 | 12 | 18 | |
4 | 24/09/2012 | 05/10/2012 | 12 | 17 | |
5 | 08/10/2012 | 19/10/2012 | 12 | 17 | |
6 | 22/10/2012 | 03/11/2012 | 12 | 14 |
Slight delay due to time spent in securing site and logistics preparation for UT at Plaza Singapura |
7 | 05/10/2012 | 19/11/2012 | 14 | 17 |