Shulou(Shulou.com)06/02 Report--

Recently, I have been thinking about some things that need to be noticed in the process of technology transfer management. Now I would like to sum up and share with you.

Core responsibilities to determine team goals

Regardless of the size of the project, there must be a goal, there must be a goal so that everyone can see the direction and clarify the meaning of daily work. Pure technical personnel should change their thinking to the overall situation, not limited to the technical level, now the individual success rather than success, the team's success is the ultimate success, we should think more about how to make the team high-quality performance output.

What resources are lacking?

At the beginning of the project, you need to know clearly what resources the team currently has, such as personnel, technical risk points, and physical hardware acquisition. Only by knowing what resources are needed can we better achieve the team goals we have set.

How to achieve this goal

This is reflected in the whole process of the project. How to achieve it, we can split it into three parts.

Business management team management technical management business management

Business management is mainly about managing the business needs that we need to deal with. In fact, we can be divided into these pieces.

Content daily task allocation and decomposition formulation of general development schedule daily understanding of development progress discussion and follow-up of specific technical issues coordination of some product requirements changes in response to some market colleagues' demand follow-up function is agile

With regard to agile development, specific practices are different for different teams and different products. However, it is important that every period of time, we need to make a summary to reflect on whether there is a bad trend in the past, and then make targeted improvements. To sum up, Agile is an attitude, not a process, an atmosphere, not a method.

The specific practice consists of the following four parts.

Planning meeting daily station meeting review meeting review meeting difficulties

There are many difficulties, or when you take up a management position, the responsibility becomes heavier, which is reflected in the following five aspects.

Requirements change online emergency handling business temporary requirements interdepartmental communication development progress risk experience timely trial product observation burnout map communication time 40-60% team management recruitment former colleagues internal recommendation technology sharing guide new people work guidance technical details code review work style and attitude non-work help mentor should be friends with new people if you are familiar with one thing, don't do it. Give it to the newcomer to encourage the newcomer to ask questions, establish a comfortable communication environment, maintain a comfortable communication environment, and appropriately guide the communication frequency and communication duration to build a private, relaxed, sincere and effective environment. Is it reasonable for two people to discuss problems together and learn from each other? is it reasonable for team activities to spend 30% of their time on technical management content? Traffic growth, whether the current architecture is competent during the activity, how much sudden traffic, whether it can withstand the pressure, how to change the architecture in the future, how to invest in which technical solutions to set up technical teams with technical pursuits, to promote the use of technology wiki, to share the promotion of code review, to pursue code quality, to think about technical challenges, to prepare in advance, to spend 10% of time.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.