Difference between revisions of "IS480 Team wiki: 2015T1 Team Big Hero 5 Metrics"
Jump to navigation
Jump to search
Xyxia.2013 (talk | contribs) |
Xyxia.2013 (talk | contribs) |
||
Line 48: | Line 48: | ||
{| class="wikitable" style="margin: auto;width:70%; text-align:center" | {| class="wikitable" style="margin: auto;width:70%; text-align:center" | ||
! style="font-weight: bold;background: #B22222;color:#ffffff; width:50px" | Iteration | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:50px" | Iteration | ||
− | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:70px" | Planned | + | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:70px" | Planned Tasks |
− | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:70px" | Actual | + | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:70px" | Actual Tasks |
! style="font-weight: bold;background: #B22222;color:#ffffff; width:50px" | Score | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:50px" | Score | ||
! style="font-weight: bold;background: #B22222;color:#ffffff; width:300px" | Actions Taken | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:300px" | Actions Taken | ||
|- | |- | ||
| 0 | | 0 | ||
− | | | + | | 2 |
− | | | + | | 2 |
| 100% | | 100% | ||
| None. We are on schedule | | None. We are on schedule | ||
|- | |- | ||
| 1 | | 1 | ||
− | | | + | | 7 |
− | | | + | | 7 |
| 100% | | 100% | ||
| None. We are on schedule | | None. We are on schedule | ||
|- | |- | ||
| 2 | | 2 | ||
− | | | + | | 4 |
− | | | + | | 4 |
| 100% | | 100% | ||
| None. We are on schedule | | None. We are on schedule | ||
|- | |- | ||
| 3 | | 3 | ||
− | | | + | | 10 |
− | | | + | | 10 |
| 100% | | 100% | ||
| None. We are on schedule | | None. We are on schedule | ||
|- | |- | ||
| 4 | | 4 | ||
− | | | + | | 12 |
− | | | + | | 12 |
| 100% | | 100% | ||
| None. We are on schedule | | None. We are on schedule | ||
|- | |- | ||
| 5 | | 5 | ||
− | | | + | | 15 |
− | | | + | | 15 |
| 100% | | 100% | ||
| None. We are on schedule | | None. We are on schedule | ||
|- | |- | ||
| 6 | | 6 | ||
− | | | + | | 6 |
− | | | + | | 6 |
| 100% | | 100% | ||
| None. We are on schedule | | None. We are on schedule | ||
Line 97: | Line 97: | ||
| 7 | | 7 | ||
| 13 | | 13 | ||
− | | | + | | 11 |
− | | | + | | 118% |
− | | | + | | 1. PM to find out the cause of delay from developers 2. Re-estimate the tasks for future iterations 3. Allocate more time for similar functionalities 4. Increase programming sessions for next iteration |
+ | |||
|- | |- | ||
| 8 | | 8 | ||
− | | | + | | 10 |
− | | | + | | 10 |
| 100% | | 100% | ||
| None. We are on schedule | | None. We are on schedule | ||
|- | |- | ||
| 9 | | 9 | ||
− | | | + | | 17 |
− | | | + | | 17 |
| 100% | | 100% | ||
| None. We are on schedule | | None. We are on schedule |
Revision as of 16:15, 5 October 2015
Schedule | Metrics | Task List |
---|
Schedule Metrics
Iterations
Iteration | Planned Tasks | Actual Tasks | Score | Actions Taken |
---|---|---|---|---|
0 | 2 | 2 | 100% | None. We are on schedule |
1 | 7 | 7 | 100% | None. We are on schedule |
2 | 4 | 4 | 100% | None. We are on schedule |
3 | 10 | 10 | 100% | None. We are on schedule |
4 | 12 | 12 | 100% | None. We are on schedule |
5 | 15 | 15 | 100% | None. We are on schedule |
6 | 6 | 6 | 100% | None. We are on schedule |
7 | 13 | 11 | 118% | 1. PM to find out the cause of delay from developers 2. Re-estimate the tasks for future iterations 3. Allocate more time for similar functionalities 4. Increase programming sessions for next iteration |
8 | 10 | 10 | 100% | None. We are on schedule |
9 | 17 | 17 | 100% | None. We are on schedule |
Bug Metrics
Iterations
Iteration | Low | High | Critical | Total Score | Actions Taken |
---|---|---|---|---|---|
2 | 0 | 3 | 0 | 15 | Use scheduled debugging time for debugging |
3 | 0 | 0 | 1 | 10 | Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled |
4 | 1 | 0 | 1 | 11 | Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled |
5 | 0 | 0 | 1 | 10 | Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled |
6 | 0 | 0 | 1 | 10 | Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled |
7 | 1 | 1 | 3 | 36 | Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled |
8 | 0 | 3 | 1 | 25 | Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled |
9 | 2 | 5 | 0 | 27 | Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled |