Agile injury-site meeting

The website will be explained in almost all books related to agile development. Although they are roughly different, they are regarded as an indispensable part of the agile development process. I personally think that the greatest significance of the website is communication, which is a mandatory communication opportunity created on the agile principle of face-to-face communication, create an opportunity for objective reasons such as personal character, time, and out-of-the-box Communication. Therefore, the website is of great significance in Agile development.

However, in the specific implementation process, some phenomena still hurt agile development.

1. The site is optional. This injury will undoubtedly cause discounts for agile development. As for how important the website is, you can simply look for the relevant books, we hope that the website will give team members a chance to get together. If no one wants to come, it will inevitably lead to information asymmetry and deviate from the agile principle. Another common understanding is that the site is a developer's business, and others may not participate. This is narrowing down the scope of the team. The agile Foundation is a multi-role team, which requires all team members to work together to complete the task. If the visual designer does not attend the site, it is not conducive to synchronization with the Development Engineer. If the tester does not participate in the station, it is not conducive to understanding the specific problems in the development process. The website will be a required option, so long as you are in this team, you must participate.

2. I don't know what the station will say. It will drag and drop the length and make it happen as needed. The purpose of the station for information synchronization is very clear, so the content is very simple. Everyone takes turns to talk about what they did yesterday, what they want to do today, and whether they need someone else to help solve a problem. In this way, it will take 30 seconds to 1 minute for each person, and the team of 10 people will not be more than 10-15 minutes. Those who start the station for 30 minutes should reflect on the situation. In fact, the station will be more important after the end of the time, for the questions raised by someone at the meeting, there will be relevant personnel to continue the discussion, and other people are disbanded. This is the important role of the website in promoting communication.

3. The website will record it as a means of checking. For project managers or some people who are responsible for management, the website record is often regarded as a means of checking the work, and the work of each member is analyzed based on the daily website record, some even ignore the risks and problems shown in the record of the website. Over time, the speech made by the team members at the website changes to a work inspection meeting.

4. There will be no content on the site. "I solved the bug yesterday and continue to solve the bug today," developers often say at the website. If this is the case, the station will not be able to play a role, we need to guide this phenomenon and analyze the problems behind it, whether it is slack or other reasons, we need to direct the content of the website to a normal track.

5. The website will be late. Being late is always inevitable, and there are always various reasons. However, we can impose a penalty for being late, so that those who are late can realize that they have delayed everyone's time and affected the team's activities. It is important to develop habits so that everyone can stay with the team. Take a team's site meeting as an example. During the iteration start meeting, the time, location, personnel, and late arrival of the site meeting will be specified, for example, if you are late, you will ask all the participants to eat chicken wings. Because of such a rule, the host can earnestly implement it. After several times, the host will not be late for almost a long time, and the website will be guaranteed to be on time.

Of course, this is not all of the above. Some people may say that this is a trivial matter and does not matter. However, when an iteration accumulates, the station will fade down and become more and more appealing. Just like the code, let the 'bad title' exist and become moldy. In the end, the entire architecture may be destroyed. Code can be rewritten, but if a problem occurs in the agile process, the cost is much higher than that of code rewriting.

-- Welcome to reprint, please indicate the source of http://blog.csdn.net/caowenbin --