3. Questions
• Each team analyzes the provided Viking product
defect data and submits a report on their findings. In
addition, each team lists their recommendations for
steps that should be taken to ensure that quality is not
an accident for the Viking project based on the defect
data (<3 pages total). As input to this exercise you
should have access to the following file:
- [Spreadsheet] Viking Project Defect Data.xls
4. Content
• The defects status to week 7
• The defects severity level to week 7
• Recomendations steps that should be taken to
ensure the quality
5. The defects status to week 7
Week 1 2 3 4 5 6 7
Open 14 20 9 19 6 9 11
Reopen
Rejected
Further Analysis
Pending
Approved 9
Assigned 7 10
Resolved 8 21
Tested 1
Close 13 44 64 70 70
Total Defect 14 35 44 63 70 79 100
6. The defects status to week 7
14
20
9
19
6 9 11
9
7 10
8
21
1
13
44
64
70
70
0
20
40
60
80
100
120
1 2 3 4 5 6 7
Open Reopen Rejected Further Analysis Pending Approved Assigned Resolved Tested Close
7. The defects status to week 7
The defects status data chart for 7 weeks
As we can see in the chart below, developers had found new defect
every week.
Especially in week 2 and 4, the defects found increase higher than
other weeks.
At the end of week 7, the total defects closed are 70/100 defects, so
we can say that the quality quite good.
10. The defects severity level to week 7
Look at the table we can see that:
- The open defects at critical level are decrease every week, but at week 7 the open defects
increase again.
- The most open defects are at the high severity level.
- The number of defects at low level are small and fixed at week 3.
- The total number of defect fix are 70/100 -> quite good.
Look at the chart we can see that:
- The defects are increase every week.
- The most of them are at the high severity level, the critical level increase fast from week 6 to
week 7.
- The low-level defects appear from week 2, stop increase and fix after that, the total amount
are not considering.
11. Recomendations steps that should be taken to ensure the quality
Understand customer’s goals:
We must defind customer’s goal, what are their expectations to the product.
Find & report potential defects:
Identify & report any new potential defect that may impact to project.
Defect Analyze:
Every defect must be analyzed by developer:
• The impact to project.
• Priority.
• Is it a real defect?
Defect Resolution:
Developers will find the way to handle defects:
• Fix defect
• Ignore defect
• Close…
12. Recomendations steps that should be taken to ensure the quality
Implement fix defects:
At this step, defect will be assigned for developers to handle and manage.
Defect Verification:
After defects are handled and manage, we will verify these defect again to ensure that they are
resolved.
Defects documentation:
Every defects whether closed or ignored, must be documented to manage and avoid the same
problem happened in the future.
Receive feedbacks from customers:
The feedback from customers are very importance because they are the end user and they will
determine whether our software are good or bad. From customers feedback we’ll know what go
wrong in our product and find the solution to fix them as soon as possible.
