After selecting a team, the project will start. From now on, I will go to work in Tianjin two days a week. In addition to project design, development, and implementation, we also hope to help T company improve its standard development team.
Busy, I can't elaborate on it, but occasionally come to this "feel and send". Interested users can click the RSS button on IE to subscribe to this blog (see the appendix for details)
In the first week, I suggest you first improve the working methods of several teams based on the problems encountered in the past:
- Unified statement: In the past, many people did not get the final message or document version because of their different email exchanges. The worst thing is that the two sides feel that they have notified the other party, but the company has not forwarded it internally, so "not on the same page ". There are two methods:
- Unified mail group. Create two contact groups, one internal group and one extended group (usually with employees outside the group or outside the company) for the project team members ). We decided to use yahoogroups for cross-company cooperation. (Www.yahoogroups.com ). To put it simply, if you want to notify everyone, you can send a yahoogroups.com email address to all members. All members can receive a reply to this email.
- Share the document directory in a unified manner. Is to open a shared directory, all related files are stored here, become the latest legal version. Conditional, you can use CMS (content management systems) with version management. We use Sharepoint. Many other shared directories are supported.
- Separation of three powers: Microsoft's R & D teams are separated by three powers: PM (Program Manager). developer. testers, three teams with direct leadership, reported directly to the product department manager (pum: product unit manager ). You can find a lot of related information on the Internet. I will not elaborate on it here. Among them, there are several key points:
- Tester is a considerable authority, and it is the signatory who finally passes the product review, because if there is a problem with the customer, the tester should first turn to the board and then the developer. Therefore, their assessment is to be able to catch a few bugs, and it is a big bug; the assessment by developers is less bugs, and they can be repaired quickly after there are bugs. Therefore, the two are enemies. If tester is led by the developer, it will become a decoration. (The following comments on current political affairs are cut down by 2500 words ).
- The program manager has a manager title, but does not care about people. This is a common misunderstanding. Company T has a team member (PM) who has worries about his lack of qualifications and technical skills. He is unable to manage the work and wants to leave. I stressed that this PM is processing PM (and feature pm), not a manager (they are called middle-level management or senior management ). When I said this, someone asked: What is the difference? I stumbled and tried to answer: "The management personnel are Party A and the employer, so the tone of speech is" I want you to do this, do that ". This PM is the coordination team and Party B, so the tone of speech is 'Big Brother, big sister; help, can you do this? So you said it would be okay to finish in three days? '".
This is because I recently started a company and had a deep understanding of Party A and Party B. I am not sure if you understand this. What about you?
- Bug Database: the main process of Microsoft's entire team is in bug database. It runs through the entire development process, initially called RAID (the famous pesticide brand-killing the enemy ?) To the current product studio. It's hard to imagine how Microsoft will survive without raid? It seems that modern manufacturers do not have ERP, and the service industry does not have CRM. Microsoft initially authorized Microsoft to release the Chinese version of the minimally invasive program in China. Later, Visual Studio had some tools. Other companies also have similar products. I will not elaborate on it here. If you have some knowledge, you can share it with you. It mainly involves integrating with the company's culture and process. This time we decided to adopt bug free (an open source version of http://www.bugfree.cn /). If the project is over, report it to you.
Attachment: subscribe to the RSS source of my blog in IE to obtain Automatic Updates:
URL: http://vincentyang.cn/blogs/vincentyang/archive/2008/10/27/610.aspx
| Tianjin project series: |
<Week 0th |
|
WEEK 1> |
