One of the Agile Development Team Management Series: Preface and starting point

This is the second article in the agile development team management series. (1, 2, 3, 4)

The previous series involved a lot of team management-related content. For example, the plug-in programming series mentioned that large teams are split into micro-development teams for management, the product management series mentioned the management of the product owner team, and the agile development performance management series mentioned the "Management Team with TCM theory ", agile development Prajna agile series has mentioned how to use the concept of "no one, no one, no sentient beings" to unite the goals of different teams in one place, and so on.

This series will focus on the management of the team. On the one hand, it will introduce the content that has been mentioned, and on the other hand, it will refer to some other content that has not been mentioned, for example, interaction between the product team and the development team, relationship between the test team and the development team, and work style can be used for reference by readers who specialize in team management.

Starting point: result-oriented

Agile development team'sExternal behaviors are result-oriented, while internal support is team work ).

The so-called result orientation refers to the result directly without being stuck in the form.

Various "forms" that can be constrained, such as methods, methods, processes, documents, departments, division of labor, responsibilities ...... Format. These forms are originally set up to help achieve better results, but if you stick to this, it may be counterproductive.

If you carefully examine the content on the right side of the agile declaration, you will find that they all belong to the form, not the result:

Individuals and interactions over processes and tools

Available Software over complete documentation

Customer collaboration over contract negotiation

Response to changes over compliance plans

These forms have guaranteed the success of many early military, aerospace, and aviation projects. However, if any project in any industry, such as the Internet industry, is stuck here, this may cause failure.

The terrible thing is that the four lines on the left are also forms rather than results. Therefore, the correct understanding of the agile declaration is:In most industries today, if results-oriented, the form on the left is better than the form on the right..

Support: Team Work

Why is team work conducive to result-oriented implementation?

An example of a brother's Yanyan attack shows that the three brothers watched the geese fly over. One said they would like to shoot them, the other said they would like to stew, and the other said they would like to fry them, the three men struggled, and the geese flew away.

For example, if there is a bug, people do not analyze how to correct and prevent it, but discuss who is responsible. For example, if there is a task, people do not analyze how to do the fastest, but discuss who should do it; for example, if there is a change, people will not analyze whether Party A and Party B are favorable before and after the change, but will discuss the processes of which departments should adopt. For example, if there is a product, people will not analyze how to make the change successful, instead, we will discuss how to assess the situation after the discussion is successful ...... It is difficult to direct the results, and it is in the dispute between departments and individuals.

This is not to say that the latter does not need to be considered, but the starting point.. If the first thought is "I", "we", "he", and "they", then teamwork cannot be established, and agile development cannot be done well.

Content of this series

This series will involve several common team relationships: product team and Development Team, design team and coding team, coding team and test team ...... And internal work style of the team.

In the meantime, we will reference several practices of teams that we have seen before and who are in it, and analyze the application environment and potential risks.