31. Do you have a daily compile?
Of course you have to do. There are three things that are necessary for software projects / product development: 1. bug management; 2. Source Control; 3. Daily build.
32. Have you accumulated a list of project risk?
want. Risk inventory. Otherwise, when the next project starts, it can only take a head to analyze Risk.
33. The more simple design is, the better
The more simple, better. There is more words when designing, it will bring endless troubles in the future. Shop should be chopped from the beginning. This is called Scope Management.
34. Try to use existing products, technology, code
Don't do something yourself. BizTalk and SharePoint are the best examples. There are two as the foundation that can increase the starting point. Or you can try as much as possible with ready-made Control. Or try to use XML instead of yourself to Parse a text file; try to use regexp instead of your own operation string, and so on. This is the embodiment of "software reuse".
35. Are you stopped to consolidate the code over a period of time?
want. It is best to one month. Learn last year, the Windows group stopped in STEVB's command to enhance security. BTW, "" This word "hang", first voice.
36. Are everyone of your project group written DAILY REPORT?
To write. Five minutes is enough, write about 10 sentences, telling yourself what I have done today. One for communication, two spur yourself (if you are free day, you will be embarrassed).
37. Do your project managers issued a Weekly Report?
want. Also communicated. The content includes current progress, possible risk, quality status, progress in various work.
38. Do you meet at least every week?
want. Be sure to meet. The programmer hates the meeting, but at least 4 hours each week is at least 4 hours. Includes Team Meeting, Spec Review Meeting, Bug Triage Meeting. Don't worry about it.
39. Do you have a record in your project group?
Meeting Request and Agenda, some people are responsible for hosting and recording, and some people will be responsible for Meeting Minutes, which is the point of Effective Meeting. Moreover, each meeting must form Agreements and Action Items.
40. What are you doing in other departments?
Send some newsflash to the entire major organization. SHOW Your Team's Value. Otherwise, when you sit in the elevator, the people in other sectors ask: "What are you doing?" When you answer the "ABC Project", others don't know, the feeling is not very good.
41. All formal communication via Email
The benefits of email are from reliance. However, it is also necessary to avoid overkill, the best way is to say first, and when email is confirmed.
42. Establish multiple Mailing Group for the project group
If you are in AD Exchange, you will build a Distribution List. For example, I will build ABC Project Core Team, ABC Project Dev Teesters, ABC Project Extended Team, and so on. This is convenient to initiate email, and people who can receive email are received, and should not be harassed.
43. Everyone knows where to find all documents?
Everyone should know. This is called Knowledge Management. The most convenient thing is to put the document in a concentrated File Share, a better way to use SharePoint. 44. Do you make a decision, tell everyone the reason?
To tell everyone the reason. One of the means of Empower Team Member is to provide sufficient information, which is one of several principles of MSF. Indeed, Tell Me why is a human condition, and Tell Me why has Understanding. Chinese people do things like to engage in restrictions, restrict information, and those who can see a document are people with identity. Big wrong. Authority, power, is not to be able to Access Information / Data, but is not to master resources.
45. Stay Agile and Expect Change
To be this. The demand will change, and the code that has been written will be modified. Do your psychological preparation, do not resist Change, but Expect Change.
