HeaderSIS.jpg

IS480 Team wiki: 2015T2 6Sigma Metrics

From IS480
Jump to navigation Jump to search
6Sigma Logo.png

Home

About Us

IS480 Management System

Project Management

Project Documentation

Schedule Metrics Task List Risks Issues Faced User Tests & Surveys

Schedule Metrics

We've adopted the following schedule metrics guidelines to help us track the progress of our project.
6Sigma Schedule Metrics.png


6Sigma New Schedule.png


6Sigma Total hours.png


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 87.5% 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 14 100% We completed the sending of email notification to sponsors. However, other notifications would be pushed to further iterations such that we can focus on Angular Material. For more information on the problems and solutions for this iteration, refer to the "Issues Faced" tab.
9 14 14 100% None. We are on schedule. However, it is important to note that there were still many bugs in this iteration, which is due to the Angular Material UI change
10 14 14 100% None. We are on schedule.
11 14 14 100% None. We are on schedule.
12 14 14 100% None. We are on schedule.
13 14 14 100% None. We are on schedule.
14 9 9 100% None. We are on schedule.

Bug Metrics

We've adopted the following bug metrics guidelines to help us in the tracking the bugs discovered in our application.
6Sigma Bugmetric.png


6Sigma Bug Metrics.png

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 0 9 3 75 Stop current development and resolve the bug immediately. Click HERE to find out more about the change management plan to Angular Material
9 0 16 0 80 Stop current development and resolve the bug immediately. Click HERE to find out more about the change management plan to Angular Material
10 4 1 1 39 The critical bug observed here was due to the SSO Service. We realized that not all smu user groups were captured in our system and hence, one faculty member could not log in. We seek technical help from IITS to retrieve all smu user groups in order to prevent this from happening again.
11 12 3 0 27 Stop current development and resolve the bug immediately.
12 9 1 0 14 Use scheduled debugging time for debugging
13 4 1 0 9 Use scheduled debugging time for debugging
14 0 1 0 5 Use scheduled debugging time for debugging

Team's Metrics

Coding Workload

6Sigma Coding workload.png

Coding Hours

6Sigma Coding Hours.png

Non Coding Hours

6Sigma Non Coding Hours.png

Total Hours

6Sigma Total Hours.png

Punch Card (GIT)

6Sigma Punch card.png