Difference between revisions of "IS480 Team wiki: 2015T1 Team Big Hero 5 Metrics"
Jump to navigation
Jump to search
Xyxia.2013 (talk | contribs) (Created page with " <!--START HEADER --> center|1000x200px <br> {| style="background-color:#414042; color:#000000 padding: 5px 0 0 0;" width="100%" cellspacing="0...") |
Xyxia.2013 (talk | contribs) |
||
(11 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | |||
<!--START HEADER --> | <!--START HEADER --> | ||
[[Image: Big_Hero_5_Logo.jpg|center|1000x200px]] <br> | [[Image: Big_Hero_5_Logo.jpg|center|1000x200px]] <br> | ||
Line 40: | Line 39: | ||
|} | |} | ||
<!---------------------------End of sub menu -----------------------> | <!---------------------------End of sub menu -----------------------> | ||
+ | |||
+ | == Schedule Metrics == | ||
+ | <br>[[Image:SMplan.png|center|800px]] | ||
+ | <br>[[Image:sm.png|center|500px]] | ||
+ | <br>[[Image:bh5finalworkinghours.png|center|500px]] | ||
+ | |||
+ | ===Iterations=== | ||
+ | {| 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:70px" | Planned Tasks | ||
+ | ! 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:300px" | 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 | ||
+ | | 9 | ||
+ | | 9 | ||
+ | | 100% | ||
+ | | None. We are on schedule | ||
+ | |- | ||
+ | | 9 | ||
+ | | 17 | ||
+ | | 17 | ||
+ | | 100% | ||
+ | | None. We are on schedule | ||
+ | |- | ||
+ | | 10 | ||
+ | | 17 | ||
+ | | 17 | ||
+ | | 100% | ||
+ | | None. We are on schedule | ||
+ | |- | ||
+ | | 11 | ||
+ | | 10 | ||
+ | | 8 | ||
+ | | 125% | ||
+ | | 1. Emergency team meeting 2.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 | ||
+ | |- | ||
+ | | 12 | ||
+ | | 11 | ||
+ | | 11 | ||
+ | | 100% | ||
+ | | None. We are on schedule | ||
+ | |- | ||
+ | | 13 | ||
+ | | 9 | ||
+ | | 9 | ||
+ | | 100% | ||
+ | | None. We are on schedule | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | == Bug Metrics == | ||
+ | <br>[[Image:BMplan.png|center|800px]] | ||
+ | <br>[[Image:bh5finalBM.png|center|500px]] | ||
+ | |||
+ | ===Iterations=== | ||
+ | |||
+ | {| 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" | Low | ||
+ | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:50px" | High | ||
+ | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:50px" | Critical | ||
+ | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:100px" | Total Score | ||
+ | ! style="font-weight: bold;background: #B22222;color:#ffffff; width:300px" | Actions Taken | ||
+ | |- | ||
+ | | 2 | ||
+ | | 0 | ||
+ | | 3 | ||
+ | | 0 | ||
+ | | 15 | ||
+ | | 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 | ||
+ | |- | ||
+ | | 3 | ||
+ | | 0 | ||
+ | | 0 | ||
+ | | 1 | ||
+ | | 10 | ||
+ | | Use scheduled debugging time for debugging | ||
+ | |- | ||
+ | | 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 | ||
+ | | Use scheduled debugging time for debugging | ||
+ | |- | ||
+ | | 6 | ||
+ | |0 | ||
+ | |0 | ||
+ | |1 | ||
+ | |10 | ||
+ | |Use scheduled debugging time for debugging | ||
+ | |- | ||
+ | |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 | ||
+ | |- | ||
+ | |10 | ||
+ | |0 | ||
+ | |0 | ||
+ | |1 | ||
+ | |10 | ||
+ | |Use scheduled debugging time for debugging | ||
+ | |- | ||
+ | |11 | ||
+ | |3 | ||
+ | |0 | ||
+ | |0 | ||
+ | |3 | ||
+ | |Use scheduled debugging time for debugging | ||
+ | |- | ||
+ | |12 | ||
+ | |2 | ||
+ | |1 | ||
+ | |0 | ||
+ | |7 | ||
+ | |Use scheduled debugging time for debugging | ||
+ | |- | ||
+ | |13 | ||
+ | |2 | ||
+ | |3 | ||
+ | |0 | ||
+ | |17 | ||
+ | |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 | ||
+ | |} |
Latest revision as of 19:18, 22 November 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 | 9 | 9 | 100% | None. We are on schedule |
9 | 17 | 17 | 100% | None. We are on schedule |
10 | 17 | 17 | 100% | None. We are on schedule |
11 | 10 | 8 | 125% | 1. Emergency team meeting 2.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 |
12 | 11 | 11 | 100% | None. We are on schedule |
13 | 9 | 9 | 100% | None. We are on schedule |
Bug Metrics
Iterations
Iteration | Low | High | Critical | Total Score | Actions Taken |
---|---|---|---|---|---|
2 | 0 | 3 | 0 | 15 | 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 |
3 | 0 | 0 | 1 | 10 | Use scheduled debugging time for debugging |
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 | Use scheduled debugging time for debugging |
6 | 0 | 0 | 1 | 10 | Use scheduled debugging time for debugging |
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 |
10 | 0 | 0 | 1 | 10 | Use scheduled debugging time for debugging |
11 | 3 | 0 | 0 | 3 | Use scheduled debugging time for debugging |
12 | 2 | 1 | 0 | 7 | Use scheduled debugging time for debugging |
13 | 2 | 3 | 0 | 17 | 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 |