16. When registering new defects, do you write a reproduction step?
want. This belongs to the communication between DEV and TEST. Face-to-face communication needs, fill in the RePro Steps in detail.
17. Do you solve the known defect before writing a new code?
want. Every person's defect cannot exceed 10 or 15, otherwise you must first solve the old BUG to continue writing new code.
18. Do you have a prior agreement on the defects?
Must be defined. Severity points 1, 2, 3, agreement: Blue Screen and Data Lost calculate SEV 1, FUNCTION Error calculates SEV 2, the SEV 3 on the interface. But this agreed can be adjusted appropriately according to the product quality status.
19. Do you have a three-country meeting to the shortcomings of opinions?
Must have. There is a clear decision process. This is similar to the concept of CCB (Change Control Board).
20. Are all defects that are closed by the registered person?
BUG should be shut down by Opener. DEV cannot close Bug privately.
21. Does your programmers disgusted to modify the old code?
Avoiding is normal. The solution is to organize the Code Review and leave the time separately. XP is also a way.
22. Do you have Team Morale Activity?
Every month must work once, eat, sing, outing, play, open kart, etc., must have. Don't save these money.
23. Do you have your project group?
Be your own logo. At least there should be its own CODENAME.
24. Does your employees have T-shirt with company LOGO?
There is. Enhance the sense of belonging. Of course, T-Shirt is better to do, preferably use 80 cotton. Don't wear a few times and break down.
25. The general manager at least participates in the sub-project group meeting at least monthly
need. Let Team Member feel that the high level pays attention to this project.
26. Are you opening a branch for each DEV?
Oppose. Branch management and Merge workload is too large, and it is easy to make mistakes.
27. Does anyone do not Check-in code for a long time?
No. For most items, you should check-in for up to two or three days.
28. Are you filled in the comment when check-in code?
To write, at least one or two sentences, such as "solve Bug No.225". If you pull high, this is also part of the "Configuration Audit".
29. Is there a final deadline for CHECK-IN every day?
To be, you have to clarify Check-in Deadline. Otherwise it will build Break.
30. Can you compile all the source code into an installation file?
need. This is the basis of daily compilation (DAILY Build). And you must be able to make automatic.
