Difference between revisions of "IS480 Team wiki: 2015T2 6Sigma Metrics"
Jump to navigation
Jump to search
Line 46: | Line 46: | ||
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 6Sigma Risks| <span style="color:#3d3d3d">Risks</span>]] | ! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 6Sigma Risks| <span style="color:#3d3d3d">Risks</span>]] | ||
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"| | ! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"| | ||
+ | |||
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 6Sigma Issues Faced| <span style="color:#3d3d3d">Issues Faced</span>]] | ! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 6Sigma Issues Faced| <span style="color:#3d3d3d">Issues Faced</span>]] | ||
+ | ! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"| | ||
+ | |||
+ | ! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 6Sigma User Surveys | <span style="color:#3d3d3d">User Surveys</span>]] | ||
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"| | ! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"| | ||
Revision as of 03:28, 24 January 2015
Schedule | Metrics | Task List | Risks | Issues Faced | User Surveys |
---|
Schedule Metrics
We've adopted the following schedule metrics guidelines to help us track the progress of our project.
Iterations
Iteration | Planned Days | Actual Days | Score | Actions Taken |
---|---|---|---|---|
1 | 14 | 14 | 100% | None. We are on schedule |
2 | 14 | 14 | 100% | None. We are on schedule |
3 | 14 | 13 | 107% | Add one day to buffer |
4 | 14 | 14 | 100% | None. We are on schedule |
5 | 14 | 16 | 114% | As we previously had an increase in buffer day from iteration 3, this resulted in a deduction of 1 day from our buffer. For more information on the problems and solutions for this iteration, refer to the "Issues Faced" tab. |
6 | 14 | 14 | 100% | None. We are on schedule |
7 | 14 | 14 | 100% | Decided to push Manipulate Statistics to further iterations. For more information on the problems and solutions for this iteration, refer to the "Issues Faced" tab. |
8 | 14 | |||
9 | 14 | |||
10 | 14 | |||
11 | 14 | |||
12 | 14 | |||
13 | 14 | |||
14 | 14 |
Bug Metrics
We've adopted the following bug metrics guidelines to help us in the tracking the bugs discovered in our application.
Iterations
Iteration | Low | High | Critical | Total Score | Actions Taken |
---|---|---|---|---|---|
1 | 1 | 5 | 0 | 26 | 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 |
2 | 1 | 1 | 0 | 6 | Use scheduled debugging time for debugging |
3 | 2 | 4 | 0 | 30 | 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 | 0 | 7 | 0 | 35 | Stop current development and resolve the bug immediately.We managed to solve the bugs before the end of iteration. Hence, project was not rescheduled |
5 | 0 | 17 | 0 | 95 | Stop current development and resolve the bug immediately. We are unable to complete bug fixing on time, and hence, we decided to use up 2 days of our buffer. Currently, we are left with 5 days of buffer after this iteration. |
6 | 0 | 6 | 0 | 30 | Stop current development and resolve the bug immediately. We managed to solve the bugs before the end of iteration. Hence, project was not rescheduled. |
7 | 2 | 8 | 0 | 42 | Stop current development and resolve the bug immediately. As too many funactionalties was breaking at this point in time, we decided to reschedule "Manipulate Statistics" to later iterations. Click HERE to find out more |
8 | |||||
9 | |||||
10 | |||||
11 | |||||
12 | |||||
13 | |||||
14 |