Difference between revisions of "IS480 Team wiki: 2015T2 6Sigma Metrics"
Jump to navigation
Jump to search
Line 169: | Line 169: | ||
|- | |- | ||
| 1 | | 1 | ||
− | | | + | | 0 |
− | | | + | | 5 |
− | | | + | | 0 |
− | | | + | | 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 |
|- | |- | ||
| 2 | | 2 | ||
− | | | + | | 1 |
− | | | + | | 1 |
− | | | + | | 0 |
− | | | + | | 6 |
− | | | + | | Use scheduled debugging time for debugging |
|- | |- | ||
| 3 | | 3 |
Revision as of 18:29, 4 November 2014
Schedule | Metrics | Task List | Risks |
---|
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 | |||
4 | 14 | |||
5 | 14 | |||
6 | 14 | |||
7 | 14 | |||
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 | 0 | 5 | 0 | 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 |
2 | 1 | 1 | 0 | 6 | Use scheduled debugging time for debugging |
3 | |||||
4 | |||||
5 | |||||
6 | |||||
7 | |||||
8 | |||||
9 | |||||
10 | |||||
11 | |||||
12 | |||||
13 | |||||
14 |