1
Found and fixed bug detection chart
FIGURE 1.2
Overall bug detection profile
600
500
Found
Found and ?¬?xed SCRs
Fixed
400
300
200
100
0
3000
2800
2600
2400
2200
2000
1800
1600
1400
1200
1000
800
600
400
200
0
Open
Open and closed SCRs
Closed
26 Mar
09 May
23 May
06 Jun
20 Jun
04 Jul
18 Jul
01 Aug
15 Aug
28 Aug
11 Apr
25 Apr
Introduction
7
8. The amount they are spending on training (because the system is unusable out of the box or the
user interface is terrible). Beware: some companies like it like this ??” users spend a lot on training
consultants and the company earns even more revenue.
9. The extraordinary number of releases made to the field. (How many major releases do they make
a year? How many minor releases, how many patches?) Rule of thumb: you should have one major
release per annum, one minor, and a maximum of two roll-up patches. Why? Because otherwise:
??? Your development and testing staff will be falling over themselves trying to get releases out,
they will be unfocused, disorganized, and chaotic, and people will leave.
??? The market will correctly perceive that your testing process, and probably much else, is
inadequate.
10. The number of developers and testers who left in the last year.
11. The overtime amount. (To cope with the chaos. Relate them to the release dates. If you can??™t
observe a pattern, then it??™s because you haven??™t been given the real release dates.
Pages:
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94