Grasp the pace in agility

Although agile has repeatedly stressed that there is only one emphasis on it, that is, customer value orientation, and the mission of providing high-quality software. However, as a department-level leader, we still need to consider how to introduce more updated things in a planned manner during the sprint to improve the team's vitality.

This was due to several recent review meetings. Everyone felt that there was nothing to say, and the problems exposed in the early stage were gradually solved. It is widely felt that the rest is to make a story one by one. Therefore, based on the current situation, I can consider introducing some new jobs, such as more professional unit tests, optimizing some frameworks, and introducing some new knowledge points. Take unit tests as an example. The team is newly established. Many people have never heard of it, but never used it. Therefore, it is not just about how to use unit test tools in the IDE, however, it is impossible to understand the usefulness of unit test and how to design and implement unit test cases reasonably and fully. If these tasks are imposed on the team at the beginning of the project, such as automatically running the unit test script after compilation, the team will feel overwhelmed. Because many team-level problems have not been solved yet, more tasks with higher priorities have not yet been done, and the process has not been straightened out yet, a sudden pressure will have a great impact on the team's morale. Therefore, we can make this auxiliary task slow down. Because the quality can be controlled by pegging and manual testing by testers. Then, after all the problems are solved, we can do some icing on the cake. unit testing is a good example. Having mastered unit testing not only helps projects, but also improves the professional quality of individuals. This is a good habit.

The same is true for the optimization framework. Because agility does not need to be fully designed at the beginning, problems that cannot be well handled by existing frameworks and technologies are constantly encountered during the development process. Maybe I couldn't come up with better suggestions for reasons such as time or ideas, so I put them on for the moment. Now that we have time and energy, we can take the time to deal with it. It is not important to start a separate story or a task containing a story. The key is that we should continue to summarize and record them at ordinary times. Once the time is ripe, we can deal with these things. Therefore, although agile focuses on doing one. But the story is okay, but the thought is no longer. Many ideas still need to be repeated in my mind. In this way, you can improve your performance, rather than simply repeating yourself.

Choosing the right time is an experience. A good grasp of the rhythm can make the entire team feel full of vigor and have a stronger desire to challenge. Otherwise, the entire team will be overwhelmed.