Internet Entrepreneurship Team 24 suggestions

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

1, do not condone the ability to lack of people. The success or failure of the project, people are absolute factors.

2, the positioning of the product is essential. It can make you spend the next year or two in vain, or you can make a lot of effort. Good product positioning, good mode choice, 8630.html "> Can sometimes let you" without pains.

3, at the start of the project, as far as possible list of work to be listed to discuss the specific implementation of the steps and possible problems, and the ability of personnel, the problems encountered and the progress of the project to do a certain assessment. Reduce project risk before the project starts.

4, record all the problems that appear in the project, as well as the follow-up work of each project member, regardless of the size of the matter. Check the problem solving situation and project schedule at any time, remind the relevant personnel to follow up the work, so that each project member of their work at their fingertips.

5, the best team is everyone can take the initiative to take their own responsibility. To achieve this goal, the team must have a consistent goal and a reasonable division of labor to ensure the interests of the team and the team members.

6. For small teams, goal based management is not as good as process based management, and process based management is inferior to human management. Objective management, can grasp the direction of the project, but easy to ignore the details. Process management, which can handle the various details in the process of target implementation, but lacks the drive of project implementation. Based on human management, the first step is to materialize the goal, become the specific implementation of the details (tasks), the second step will be detailed to the specific person, clear the corresponding rights and responsibilities, as well as mutual communication and coordination of methods, the third step for each task set time limit, progress control. A project must have a project catalyst, he defined the needs and objectives of the project, can understand and accept each project members to do the work, to help project members to solve their own problems, so that the project at the specified point in time to be completed. Highly vigilant, able to pre-project deviations and corrective actions.

7. If you want your team to be a close cooperative group, don't compete within the team. Any competition will cause tension within the team. Bad words can lead to loss of team members. Even though some of the competition is benign, it is within the team. Encouragement and cooperation are more effective than competition.

8. Do not expect everyone to take the initiative to do things that are not assigned to him. A project member will only do what he knows to do or within his purview. So tell the project team exactly what to do and what to do with it. This can reduce the discrepancy between the reciprocal push Committee and the scope of work leads to omissions.

9, cause and effect is inevitable. All neglected, shelved, compromised, and considered problems will be in the form of errors, bugs, rework, constraints, and so on. So when you see the problem, you have to work it out immediately.

10, let the project members understand each other's work, as well as the specific methods of implementation. Especially the procedure. This can greatly reduce the problems caused by the deviation of understanding and the conflict of realization.

11, to give the program a clear, comprehensive needs and time to think fully, this can reduce some of the implementation of unnecessary errors.

12, tell the project members should have the ability, as well as the follow-up direction of development. Help at work or remind them to consciously improve their abilities. This will strengthen the cohesion of the team.

13, communication is actually very easy, to help others do something, or to ask someone some questions, are very good communication methods.

14, let others understand you and the initiative to understand others equally important.

15. A moderate quarrel helps to communicate. A simple way to solve a quarrel, let both sides put their own views and reasons to list, weigh or find a more reasonable way. Transposition thinking and keeping an open mind is an effective way to resolve disputes.

16, positive treatment of adverse news. Maintain team morale and member motivation.

17, in understanding the ability of team members on the basis of appropriate authorization, so that they have the right or initiative to solve some unexpected problems.

18. Do not concentrate the key resources of the project on one person. Try to avoid situations where a person's project is missing from the team.

19, for a project, the loss of personnel to the project caused by the losses are huge, the loss of backbone personnel may be fatal to the project hit. So try to ensure the integrity of your team.

20, give anyone the opportunity. Only with full understanding can we evaluate it correctly.

21, can evaluate a person's performance with the result, but it is best not to evaluate one's ability or potential with the result. Make a mistake and give someone the chance to pay their tuition.

22. The analysis process is as important as knowing the conclusion. When you understand how team members think about something, ask a few questions: Why do you think that helps to make you understand his abilities and ideas more clearly?

23, cultivate your team, so that each project members have a good habit and the way to deal with things, mentality. Force your program to develop good programming habits.

24, pay attention to the user experience. Find where products can be improved by using every nuance of the user's experience. In the development of demand, must be the necessary details, the setting of human words, the user experience is very important things, write to the main needs. Treat these requirements as part of the realization of the subject. Do not show the product implementation, and then use the test, and then comment on the details of the improvement, this can effectively save the later product improvement, debug time spent.