HeaderSIS.jpg

IS480 Team wiki: 2013T2 GENShYFT Project Management metric

From IS480
Jump to navigation Jump to search

GENShYFT IS480 1314 Logo.jpg


Home   Project Overview   Project Management   Documentation   The Team


Overview   Risk   Schedule   Metric   Minutes


Schedule Metric


Genshyft is480 1314 metric1.JPG

Bug Metric


Genshyft is480 1314 metric2.JPG


Schedule Metrics

The objective of Schedule Metrics is to help the team to keep track of the progress of our project development.
The Schedule Metrics will be tracked by the Project Manager on per Iteration basis.

The following formula is used by the team to calculate Schedule Metrics (SM):
Schedule Metrics (SM) = Estimated time / Actual time
*time is measured in Days

Score(%) Description Action
SM > 1.3

Team is way behind schedule

Very behind schedule. PM to conduct review to determine the cause of delay and to reschedule project. Consider dropping functionalities.

1.1<=SM<=1.3

Team is behind schedule

Behind schedule. PM to conduct review to determine the cause of delay. Bring delayed tasks into the next iteration and to reschedule project. Can choose to overload more tasks in the next iteration or push into buffer time

0.9<=SM<=1.1

Team is on track

Currently on track. Keep up with the progress.

'0.7=<SM<=0.9

Team is ahead of schedule

Ahead of schedule. Review schedule and decide whether it is possible to bring forward tasks from next iteration to current iteration

150 < SM

Team is way ahead of schedule

- Project Manager to find out from developers on why tasks are completed earlier than expected and ensure that quality of the application is not compromised
- Start on next task earlier
- PM to reduce the time required for similar tasks for the future iterations
- Add the number of days gained to buffer days