IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics
Revision as of 09:07, 14 February 2016 by Choryi.poon.2012 (talk | contribs)
Schedule | Schedule Metrics | Bug Metrics | Risk Management | Change Management |
---|
Schedule Metric Score & Description
Iteration | Estimated no. of days | Actual no. of days | Metric Score | Description |
---|---|---|---|---|
1 | 8 | 8 | 1.00 | Our estimates are fairly accurate. Project schedule is on track. No action required |
2 | 10 | 10 | 1.00 | Our estimates are fairly accurate. Project schedule is on track. No action required |
3 | 10 | 10 | 1.00 | Our estimates are fairly accurate. Project schedule is on track. No action required |
4 | 15 | 15 | 1.00 | Our estimates are fairly accurate. Project schedule is on track. No action required. |
5 | 10 | 11 | 0.91 | Our estimates are fairly accurate. Project schedule is on track. 1 buffer day used to debug Email Access Codes due to complexity in number of possible scenarios with different type of users (students) |
6 | 12 | 12 | 1 | Our estimates are fairly accurate. Project schedule is on track. No action required. |
7 | 12 | 12 | 1 | Our estimates are fairly accurate. Project schedule is on track. No action required. |
8 | 13 | 14 | 0.93 | Our estimates are fairly accurate. Project schedule is on track. No action required. |
9 | 12 | 9 | 1.33 | Iteration ended early as Batch Report module was pushed back due to client's inability to provide algorithm on time. Team decided to change schedule and Supervisor was informed of changes. |
10 | 10 | |||
11 | ||||
12 | ||||
13 | ||||
14 |