Difference between revisions of "IS480 Team wiki: 2016T2 ProgneSIS Bug Metrics"
Jump to navigation
Jump to search
(13 intermediate revisions by the same user not shown) | |||
Line 89: | Line 89: | ||
==<div style="background: #7f7f7f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Bug Metrics Score</font></div>== | ==<div style="background: #7f7f7f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Bug Metrics Score</font></div>== | ||
− | <center>View our | + | <center>View our bug log [[Media: Team_ProgneSIS_Bug_Log.pdf|here.]]</center><br> |
[[Image:Team_ProgneSIS_Bug_Metrics_Score_Graph.png|center|700px]] | [[Image:Team_ProgneSIS_Bug_Metrics_Score_Graph.png|center|700px]] | ||
+ | |||
+ | ==<div style="background: #7f7f7f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Bugs by Category</font></div>== | ||
+ | [[Image:Team_ProgneSIS_Bugs_by_Category_Graph.png|center|700px]] | ||
==<div style="background: #7f7f7f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Bugs Summary(by Iteration)</font></div>== | ==<div style="background: #7f7f7f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Bugs Summary(by Iteration)</font></div>== | ||
Line 106: | Line 109: | ||
|- | |- | ||
|2 | |2 | ||
− | |<b> | + | |<b>6</b> <br> 1 High <br> 1 Low<br> |
− | | | + | |1 high bug was due to the missing plots although the JSON format is returned correctly. 1 low bug was due to the datepicker not showing what the user has selected. |
− | | | + | |Developers to use planned debugging time in the iteration to solve the bug. |
|- | |- | ||
|3 | |3 | ||
− | |<b> | + | |<b>0</b> <br> 0 High <br> 0 Low<br> |
− | | | + | |No bugs as this iteration is used for change management. |
− | | | + | |The team did major changes in scope. |
|- | |- | ||
|4 | |4 | ||
− | |<b> | + | |<b>0</b> <br> 0 High <br> 0 Low<br> |
− | | | + | |No bugs as the UI is not up for testing. |
− | | | + | |Only the backend development is done. |
|- | |- | ||
|5 | |5 | ||
− | |<b> | + | |<b>6</b> <br> 1 High <br> 1 Low<br> |
− | | | + | |1 high bug was due to inaccuracy in date conversion. 1 low bug was due to no indication when there's no data for time period. |
− | | | + | |Developers to use planned debugging time in the iteration to solve the bug. |
|- | |- | ||
|6 | |6 | ||
− | |<b> | + | |<b>6</b> <br> 1 High <br> 1 Low<br> |
− | | | + | |1 high bug was due to users unable to change password. 1 low bug was due to calculation error in performance growth. |
− | | | + | |Developers to use planned debugging time in the iteration to solve the bug. |
|- | |- | ||
|7 | |7 | ||
− | |<b> | + | |<b>6</b> <br> 1 High <br> 1 Low<br> |
− | | | + | |1 high bug was was due to customers unable to change password. 1 low bug was due to the display of information although selected time period does not have data. |
− | | | + | |Developers to use planned debugging time in the iteration to solve the bug. |
|- | |- | ||
|8 | |8 | ||
− | |<b> | + | |<b>10</b> <br> 2 High <br> |
− | | | + | |2 high bugs were due to 1) Customer unable to login at times, 2) Data was displayed for customers even during time period without data. |
− | | | + | |The team has to stop all current development and resolve the bug immediately. |
|- | |- | ||
|9 | |9 | ||
− | |<b> | + | |<b>5</b> <br> 5 Low <br> |
− | | - | + | |5 low bugs were cosmetics - the way the lowest level graphs from the 5 dimensions are displayed. |
− | | | + | |Developers to use planned debugging time in the iteration to solve the bug. |
|- | |- | ||
|10 | |10 | ||
− | |<b> | + | |<b>10</b> <br> 1 Critical <br> |
− | | | + | |1 critical bug was due to screen scrape being unable to function on server due to overconsumption of memory. |
− | | | + | |Although it was a critical bug, there were no other development to be done, thus, developers used planned debugging time in the iteration to resolve the bug. |
|- | |- | ||
− | |11 | + | |11 & 12 |
− | |<b> | + | |<b>0</b> <br> 0 High <br> 0 Low<br> |
− | | | + | |User testings were conducted to collate information that sponsor could use to enhance the application as team would not have sufficient time to implement major changes at this stage. |
| - | | - | ||
− | |||
|} | |} | ||
<br> | <br> | ||
<!--Content End--> | <!--Content End--> |
Latest revision as of 15:57, 9 April 2016
Project Schedule | Schedule Metrics | Task Metrics | Bug Metrics | Risk Management | Change Management |
|
Iteration | Bug Score | Summary of bugs | Action Taken |
---|---|---|---|
1 | 26 1 Critical 3 High 1 Low |
1 critical bug was due to undefined session. 3 high bugs were due to incorrect logic to get accurate figures. | The team has to stop all current development and resolve the bug immediately. |
2 | 6 1 High 1 Low |
1 high bug was due to the missing plots although the JSON format is returned correctly. 1 low bug was due to the datepicker not showing what the user has selected. | Developers to use planned debugging time in the iteration to solve the bug. |
3 | 0 0 High 0 Low |
No bugs as this iteration is used for change management. | The team did major changes in scope. |
4 | 0 0 High 0 Low |
No bugs as the UI is not up for testing. | Only the backend development is done. |
5 | 6 1 High 1 Low |
1 high bug was due to inaccuracy in date conversion. 1 low bug was due to no indication when there's no data for time period. | Developers to use planned debugging time in the iteration to solve the bug. |
6 | 6 1 High 1 Low |
1 high bug was due to users unable to change password. 1 low bug was due to calculation error in performance growth. | Developers to use planned debugging time in the iteration to solve the bug. |
7 | 6 1 High 1 Low |
1 high bug was was due to customers unable to change password. 1 low bug was due to the display of information although selected time period does not have data. | Developers to use planned debugging time in the iteration to solve the bug. |
8 | 10 2 High |
2 high bugs were due to 1) Customer unable to login at times, 2) Data was displayed for customers even during time period without data. | The team has to stop all current development and resolve the bug immediately. |
9 | 5 5 Low |
5 low bugs were cosmetics - the way the lowest level graphs from the 5 dimensions are displayed. | Developers to use planned debugging time in the iteration to solve the bug. |
10 | 10 1 Critical |
1 critical bug was due to screen scrape being unable to function on server due to overconsumption of memory. | Although it was a critical bug, there were no other development to be done, thus, developers used planned debugging time in the iteration to resolve the bug. |
11 & 12 | 0 0 High 0 Low |
User testings were conducted to collate information that sponsor could use to enhance the application as team would not have sufficient time to implement major changes at this stage. | - |