After such a long period of agile development, I was deeply impressed with a sprint for the first time. I think the main reasons are as follows. First, there is a brand new team consisting of very young people who have hardly experienced any formal procedures. Second, we are forced to pull a lot of basic work into the backlog without explicit columns. Third, from the demand to the technology to the deployment, they are not prepared at the beginning, and they are all iterated over time.
Team. Chatting with any experienced scrum master will make me feel that not everyone is agile. Agility has high requirements on people. In the past, when I was doing a traditional process, I often felt that I had dug a hole and then filled in the radish. Radish is only responsible for quietly growing up in a certain pit. agile means that the entire team is digging holes. Whoever is right will take the initiative to jump in and fill holes, jump out and find a suitable trap. Agility is very time-sensitive for communication. One problem is that you decide when to throw it out and how to choose the best communication method, mail, phone, or IM. There is also the accuracy of expression. If you cannot clearly express a problem, the team will not be able to help you solve it. Over time, you will become more accustomed to solving it by yourself. Without knowing it, it is isolated.
Implicit tasks. The agile burndown chat is very helpful. Because the concept of agility is only time-based, it is necessary to fully visualize what is done at a certain time. This not only makes all stakeholders clearly understand what you are doing, but also makes everything easier to manage. Otherwise, the data accumulated by each sprint is meaningless for future plans.
Changes and iterations. I want to choose agility, and I must embrace changes. It is too important to manage changes in a sprint. In the face of any changes and any external impact, I think we must keep in mind a core goal, that is, to receive stories. We need to use our brains to make a careful analysis and come up with a way to complete the task in the shortest time. For example, if some basic components are still under synchronization development, we need to lock the versions of these components in daily development to isolate their unstable parts, use various false objects and other methods to make necessary encapsulation. You also need to carefully discuss the changes in requirements with the Po to see if the changes are real-time or can be put in the future. It is learned a lot. I think this is not clear in words, but it is brought about by the accumulation of project promotion experience. Playing agile is really an experience. Because agility itself has no methodology. It has only a few core concepts, and how to understand it depends on the individual.
The review meeting will be held tomorrow. I think everyone must have a lot to say. I like this collision very much, because it gives me a more comprehensive understanding of agile running in various ecological environments.