HeaderSIS.jpg

IS480 Team wiki: 2013T1 Kungfu Panda Schedule Metrics

From IS480
Revision as of 10:50, 3 October 2013 by Yh.koon.2010 (talk | contribs)
Jump to navigation Jump to search
KP-Header.PNG
Home About Us Project Overview Project Management User Testing Project Documents


Project Progress Our Milestones Metrics Management Risk Assessment Changes


Schedule Metrics

The main objective of our schedule metrics is to keep track of our project process closely. The schedule metric is measured at the end of each iteration and the project manager will proceed to discuss with the team members on the actions which is needed and to manage the project schedule.

This is how we measure our schedule metrics:

KP-ScheduleMetrics.png



KP-Individule MetricsWk23.PNG



Below are some graphs which shows our schedule metrics for each iterations and for the individual members.
We have also calculated the average man hours per week each member put in.

KP-TeamScheduleMetricsWk23.PNG


KP-Individule MetricsGraphWk23.PNG


KP-ManhoursWk23.PNG



Bug Metrics


The Bug Metric is to help us keep track of the current bugs we have for each week. The bug metric is measured every Saturday of the week. This is because, we set aside Sunday as a buffer day for us to solve the bugs when our bug metrics exceed 10 points. This measurement helps us to ensure that we resolve our current bugs soon before we move on with our development.

Total number of bugs encountered: 31
Bug Metric for FYP Week 21: 12 KP-BadBugMetric.PNG

KP-BugMetricsNew.PNG


KP-BugMFormula.PNG


KP-Bug Metrics wk23a.PNG


KP-Bug Metrics wk23b.PNG