I work for a small software company with less than 10 programmers. Our software is installed in dozens of locations around the world. Our code base is huge, mainly due to poor design and a lot of code duplication (IMO). We have about 30 different projects, each of which contains about 600 KLOC, and about 200 KLOC is our own homegrown code. When I got there in 2006, this code was not even version controlled. I managed to convince the authorities that this was important, and now we use a code management system (cs-rcs, not my choice, but better than nothin), and an error tracking system. The huge missing piece is the complete and complete absence of QA in this process. Our release does not exist on paper, and in practice it consists of "hit ctrl-F9,copies the binary to the client, declares the problem fixed. "
Can someone point me to some official documents or documents or articles in the PHB language that can explain the blatant insanity in the process? I am sure that the boss can hire a consultant to tell him about it, and then he could believe it. But I'm just a humble developer with a BS Software Software degree. And my ethnicity doesn't help me either. What are the best ammunition to use in this case?
Tautologically, the only way to convince them is to set something convincing in front of you. This can be done from a list, for example:
- . - - QA, , -, , . , .
. " " .
? , ?
Google " ", .
, , ( ), , . .
. , , , , , .
PHB "", "" . - - .
, , . , , QA, , .
- - , . , : http://www.developertesting.com/images/entryimages/paradox-figure3.jpg( www.developertesting.com)
, : (1) (2) . , . $40 . $60 . , . , , 2 , 100k .
... , , . , , , , . , , - , . - , , . , , ( , , ), . , ( ) , .
The Toyota Way. - toyota. , , , . , , . - Toyota Long Drive ( , PDF ).
, - , . , , , .
Joel book
, QA , - " " , , , - , .
, , , , , .
, . :
, .