Agile Project Development Method

Agile teams mainly adopt the following methods:

Work as a whole; Work by segment iteration cycle; deliver some results for each iteration; pay attention to the business priority; check and adjust.

1. agile groups work as a whole and strive for a goal. This is the key to the success of the entire team. If all the team members have their own thoughts, the team's cohesion and work efficiency will be greatly reduced. There is also a division of labor in the agile team, a project manager, an architect, an analyst, a designer, a developer tester, and so on. Each has a self-responsible task. However, they do not work independently. Architects, developers, and project managers may work with analysts to analyze the customer's needs. Designers, architects, and developers may work together to design. The entire team has different division of labor, but they work as a whole. There will never be a requirement analyst who directly gives the analysis structure to the designer, nor will the designer directly throw the design to the developer. Software development is a highly intelligent and creative labor. Like the management process, the development process cannot become an industrial production line. They have essential differences.

What are the important roles of an agile team? I think there should be at least three types of project managers, technical directors, and other team members. Other team members include requirement analysts, designers, developers, and testers. Of course, in the actual situation, the design and development personnel may refer to the same person.

The project manager must act as the product owner and sheepdog. First, the project manager should be responsible for the success or failure of the entire project, project benefits, project costs, and so on. The interests of the entire project and the project manager are closely related. The project manager has the most contact with the customer, so the Project Manager also accepts or rejects the team's results on behalf of the user to determine the priority of the user story.

In addition, the project manager should also act as a sheepdog to protect the herd against attacks and interference from wolves, so that the herd can eat grass with peace of mind. Who is the wolf? Some transactions that have an impact on team efficiency can be called Wolf. For example, it may take three days for a superior to lead a team to do another task. This is a wolf, which interferes with the normal life of the herd. As a dog, the Project Manager will try his best to eliminate these issues. For example, the marketing department requires that a function be demonstrated in the next month. However, depending on the team's capabilities, it may take next month to complete this function, so the project manager should also remove these obstacles, do not affect the normal development of the team.

Why should the technical director of the Team be taken out specially? Because the quality of the system is too important. It is important that we have no room for discussion. Quality is generally divided into internal quality and external quality. Internal Quality refers to the systemCodeStructure, Code definition, scalability, and ease of use are invisible to users. The external quality mainly refers to whether the system interface is beautiful, whether there is progress information in a processing process, and whether it meets the user's operation habits. The external quality can be compromised sometimes, but the internal quality cannot be compromised at any time. Ensure internal quality. This also reflects the importance of the technical director.

 

What role does the Team Technical Director play in the herd? Leader! As we all know, sheep are a very gentle animal, so as a leader should not be forced to manage the team, but to influence the team. The Technical Director should guide the technical work of the entire team, conquer the entire team with his own abilities and charm, and lead the team members to conquer technical difficulties. At the same time, the leader is also responsible for the quality of the entire project.

The team is a herd. under the protection of the sheepdog and under the leadership of the leader, there is only one goal, that is, to eat as much grass as possible. Our team has only one goal to deliver the most valuable products to users. High-quality teams must have high-quality members, so they must be able to manage themselves well. Otherwise, agile teams will be greatly damaged. When someone cannot adapt to agile teams or manage themselves, the team has the right to invite him out of the team.

2. agile teams work in short iterations. In Agile development, there are no important concepts for the project stage, such as the requirement analysis interface, outline design stage, detailed design stage, coding stage, and test stage. These processes are distributed in each iteration cycle. It does not mean that the Agile Development Department has no document and agile design requires a design with higher quality and more flexibility. As for documents, only necessary documents and clear requirements are required, design that is important and has a major impact on the design of the system may need to be documented, and others may not. To write all-around documents, it is better to improve the readability of the Code, increase the key gaze, and improve the design documentation.Source codeDesign.

Generally, an agile iteration process is two to six weeks. Of course, this time is scalable and can be determined based on your actual situation. However, the iteration process must have a clear end line. Otherwise, developers will fall into a long and untargeted long journey, this will affect the team's enthusiasm and work efficiency. In addition, the plan cannot be corrected for a long time. Review and the entire development route cannot be corrected. A series of problems may also occur.

3. The agile team will deliver some results each iteration. Each iteration of the agile team is a complete requirement acquisition, analysis, design, coding, testing, and so on. The goal of an agile iteration is to submit some valuable functions to users. After these results are delivered to the customer, the customer puts forward new requirements and suggestions for modification during use. The agile team will implement them in the following iteration process.

4. agile teams focus on business priorities. The agile Group focuses on the priority of the business, because these features with higher priority can better reflect the value of the user. When organizing user needs, they also need to be organized by priority. Agile requirements are based on user stories to organize user needs. A user story is a brief description of functions from the perspective of system users.

5. The agile team conducts self-check and adjustment. The reason for the plan is that they have some uncertainty before the formal implementation. Just like when we are at sea, we can only guess the previous situation based on the current situation without looking beyond the horizon. But the result of the guess is not necessarily correct. Therefore, we must continue to move forward. The sudden changes in user requirements and unexpected bottlenecks in the implementation of new technologies are all factors that force us to perform self-check and adjustment.

Therefore, in the iteration process, especially after an iteration, it is necessary to summarize the experience and lessons in the previous iteration in a timely manner, even if the development status and speed are adjusted.