IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Metrics
|Project Schedule||Schedule & Bug Metrics||Gender Recognition Metrics||Risk Management||Minutes Repository|
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 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.
|2||03/09/2012||08/09/2012||5||10||*length of iteration 2 is half of iteration 1|
*difficulties in implementing neural network