HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T1 Kungfu Panda Schedule Metrics"

From IS480
Jump to navigation Jump to search
Line 49: Line 49:
 
===Schedule Metric===
 
===Schedule Metric===
 
<br/>
 
<br/>
[[Image:KP ScheduleMetric Plan.PNG|686x254px]]
+
[[Image:KP ScheduleMetric Plan.PNG|686x254px|centre]]
 
[[Image:KP ScheduleMetric a.PNG|1012x418px]]
 
[[Image:KP ScheduleMetric a.PNG|1012x418px]]
 
[[Image:KP ScheduleMetric b.PNG|1012x418px]]
 
[[Image:KP ScheduleMetric b.PNG|1012x418px]]
[[Image:KP ScheduleMetric Inv.PNG|767x318px]]
+
[[Image:KP ScheduleMetric Inv.PNG|767x318px|centre]]
[[Image:KP ScheduleMetric Team.PNG|1012x418px]]
+
[[Image:KP ScheduleMetric Team.PNG|768x271px|centre]]
  
 
===Hours Per Week Metric===
 
===Hours Per Week Metric===

Revision as of 19:02, 24 November 2013

KP-NewHeader.PNG
Home About Us Project Overview Project Management User Testing Project Documents


Project Progress Our Milestones Metrics Management Risk Assessment Changes


Scheduling 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-ScheduleMetricsNew2.PNG



KP-ScheduleMetrics(a) wk 29.PNG
KP-ScheduleMetrics(b) wk 29.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-TeamScheduleMetricsWk29.PNG


KP-Individule MetricsGraphWk29.PNG


KP-ManhoursWk29.PNG



Schedule Metric


KP ScheduleMetric Plan.PNG

KP ScheduleMetric a.PNG KP ScheduleMetric b.PNG

KP ScheduleMetric Inv.PNG
KP ScheduleMetric Team.PNG

Hours Per Week Metric


Hours Deferred Metric


Bug Metric


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.


Bug Metric for FYP Week 30: 0 KP-GoodBugMetric.PNG

KP-BugMetricsNew2.PNG


KP-BugMFormula.PNG


KP BugCalculation.PNG


KP BugMetric-a.PNG


KP BugMetric-b.PNG


KP BugMetric-c.PNG


Happiness Metric


Happiness is an important factor as it motivates the team to work harder for our FYP project. There are time some may affected by external factors but we hope that everyone in our team always keep their smile. This metric is to measure how happy is the team in average and we measure it weekly during our team’s weekly meeting.

The scale is shown below. Every member will choose the facial which represent their feeling. According to the score from each member, we will calculate using the formula as shown below.

KP-HappyMetirc.PNG
KP-HappyMetircScale.PNG


KP Happy Metric New.PNG