Difference between revisions of "IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics"
Jump to navigation
Jump to search
Line 90: | Line 90: | ||
| style="text-align:center" | 11 | | style="text-align:center" | 11 | ||
| style="text-align:center" | 1 | | style="text-align:center" | 1 | ||
− | | style="text-align:center" | Our estimates are fairly accurate. Project schedule is on track | + | | style="text-align:center" | 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) |
|- | |- | ||
Line 109: | Line 109: | ||
| style="text-align:center" | 8 | | style="text-align:center" | 8 | ||
| style="text-align:center" | 13 | | style="text-align:center" | 13 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | 14 |
| style="text-align:center" | 1 | | style="text-align:center" | 1 | ||
| style="text-align:center" | Our estimates are fairly accurate. Project schedule is on track. No action required. | | style="text-align:center" | Our estimates are fairly accurate. Project schedule is on track. No action required. | ||
Line 115: | Line 115: | ||
|- | |- | ||
| style="text-align:center" | 9 | | style="text-align:center" | 9 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | 12 |
− | | style="text-align:center" | | + | | style="text-align:center" | 9 |
| style="text-align:center" | - | | style="text-align:center" | - | ||
− | | style="text-align:center" | Batch | + | | style="text-align:center" | 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. |
|- | |- | ||
| style="text-align:center" | 10 | | style="text-align:center" | 10 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | 10 |
| style="text-align:center" | | | style="text-align:center" | | ||
| style="text-align:center" | | | style="text-align:center" | | ||
Line 129: | Line 129: | ||
|- | |- | ||
| style="text-align:center" | 11 | | style="text-align:center" | 11 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | |
| style="text-align:center" | | | style="text-align:center" | | ||
| style="text-align:center" | | | style="text-align:center" | | ||
Line 136: | Line 136: | ||
|- | |- | ||
| style="text-align:center" | 12 | | style="text-align:center" | 12 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | |
| style="text-align:center" | | | style="text-align:center" | | ||
| style="text-align:center" | | | style="text-align:center" | | ||
Line 143: | Line 143: | ||
|- | |- | ||
| style="text-align:center" | 13 | | style="text-align:center" | 13 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | |
| style="text-align:center" | | | style="text-align:center" | | ||
| style="text-align:center" | | | style="text-align:center" | | ||
Line 150: | Line 150: | ||
|- | |- | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | |
| style="text-align:center" | | | style="text-align:center" | | ||
| style="text-align:center" | | | style="text-align:center" | | ||
| style="text-align:center" | | | style="text-align:center" | | ||
<!--CONTENT END--> | <!--CONTENT END--> |
Revision as of 09:00, 14 February 2016
Schedule | Schedule Metrics | Bug Metrics | Risk Management | Change Management |
---|
Schedule Metric Score & Description
Sprint | 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 | 1 | 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 | 1 | Our estimates are fairly accurate. Project schedule is on track. No action required. |
9 | 12 | 9 | - | 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 |