These seventy-five, are the summary of the experience of the experience in Microsoft for two years, in the case of how to write quality software with the right way. Perhaps look like a strange, but the sound of the sound, this seventy-five utility, not necessarily, not there is a few hundred pages of system, but far more than that:
1. Have your project group use the source code management tool? 2. Is your project group use the defect management system? 3. Is your test group still write test cases with Word? 4. Does your project group have a portal? 5. Do you have the best tool you can buy? 6. Is your programmer working in a quiet environment? 7. Does your employees have a phone call? 8. Everyone knows who you should find out? 9. You have encountered someone say "I thought ..."? 10. Are all people in your project group sitting together? 11. Does your progress table reflect the latest developments? 12. Is your workload to be estimated by everyone? 13. Do your developers work overtime from the beginning of the project? 14. Is the buffer time in your project plan? Is it behind every small task? 15. It is worth more to spend some time, from 95% to 100% good 16. Do you write a reproduction step when registering new defects? 17. Do you solve the known defect before writing a new code? 18. Do you have a prior agreement on the defects? 19. Do you have a three-country meeting to the shortcomings of opinions? 20. Are all defects that are closed by the registered person? 21. Does your programmers disgusted to modify the old code? 22. Do you have Team Morale Activity? 23. Do you have your project group? 24. Does your employees have T-shirt with company LOGO? 25. The general manager participated in a project group meeting at least monthly monthly monthly monthly monthly monthly monthly monthly. 27. Does anyone do not Check-in code for a long time? 28. Are you filled in the comment when check-in code? 29. Is there a final deadline for CHECK-IN every day? 30. Can you compile all the source code into an installation file? 31. Do you have a daily compile? 32. Have you accumulated a list of project risk? 33. The smoother the design, the better 34. Try to use existing products, technology, code 35. Are you stopping a consolidation code over a period of time? 36. Are everyone of your project group written DAILY REPORT? 37. Do your project managers issued a Weekly Report? 38. Do you meet at least every week? 39. Do you have a record in your project group? 40. What are you doing in other departments? 41. All formal communication 42 is made through Email. Establish multiple mailing group43 for the project group. Everyone knows where to find all documents? 44. Do you make a decision, tell everyone the reason? 45. Stay Agile and Expect Change46. Do you have a full-time software tester? 47. Do you have a general plan to specify what to do and how to do? 48. Do you write Test Case first and then test it? 49. Will you create test cases for various input combinations? 50. Can your programmers see test cases? 51. Do you have someone else to do any useful test? 52. Are you the expectation of automatic testing? 53. Does your performance test do all functions have been done? 54. Have you noticed the insecticide effect in the test? 55. Is there anyone in your project group to say the current overall quality of the product? 56. Do you have a unit test? 57. Your programmer throws the wall after writing the code? 58. Are all functions in your program have input checks? 59. Does the product have a unified error handling mechanism and an error interface? 60. Do you have a unified code writing norms?
