Progressive Agility-Daily meetings

Through the implementation of a period of time, the daily meeting also achieved good results, we also understand that each need to do

Work matters.

Daily meetings in agile development are designed to determine the work to be performed on the next day in order to fulfill their commitments to the maximum possible. Each member of the team should describe the work that has been done since the last meeting. They plan to work on the day and any issues or problems that may affect other team members or require assistance from other team members. to ensure that the meeting starts on time and ends in minutes or less. in this meeting, each team member needs to answer the following three questions:

　　What work did I finish yesterday?  

What will I be doing today?  

What blocking issues or obstacles may affect my work?

However, in the daily routine implementation of the process also encountered a variety of problems, so now summarize.

1. meeting cannot be held on time

Question: It was in the morning, but the old one was late, and there was no requirement to be late. Even if everyone is on time to work, it will be due to a variety of procrastination, leading to the meeting can not be held on time.

Solution: Then we put it in the afternoon, before work , ten minutes ahead of time to remind. After this adjustment, the effect is really good. So determine a suitable time for everyone to form habits and rules, adhere to the implementation. There can be incentives and penalties for measures.

2. Non-concern

Question: At first, everyone was talking about their own things, how much they were doing, and what they were going to do. When a person speaks, others are thinking about their own things. After they have finished their work, they are still confused about what other people have to do and what they have to do.

Solution: In order to solve this problem, the daily Legislative Council on the use of random questions on the way to improve the Legislative Council, the basic form is, in the daily meeting, when a person is finished, randomly take a person to ask questions, asked what has just been said, there is no understanding. This person should plainly say what the person said, if not to say, let this person to the person who just spoke to inquire and understand. Other people are watching these two people for dialogue, until the people who do not understand can say it clearly, if you do not understand, continue to ask. After a period of time, found that the effect is good, everyone's mood suddenly lifted up, the atmosphere is also lively up.

3. describe ambiguity

Question: If there are vague words in the speech of the Legislative Council, there is a need to draw attention to the ambiguities which may actually be a place to be noticed. For example, "already almost finished", "This task is a little complicated", "encountered a little trouble", "yesterday to get something else delayed", "there is a problem, need to rewrite" and so on. It is reasonable to listen and feel justified, for a number of reasons, which lead to delays in today's tasks, but a careful thought that led to these problems not being discovered in time. These are the places where the problems are actually.

　　Solution: If there is a vague vocabulary, pause, ask, almost how much, where there is a problem, why need to rewrite, what small trouble?? This is the real problem to ask, timely correction and provide help, ambiguous place to be confirmed, to avoid developers with doubts to develop. there should be no vague words in the Legislative Council. However, it is important to note that the tone and attitude of the inquiry need to grasp the purpose of the inquiry is to know what is the reason for the vague, is to help employees, for the efficiency of the whole team, rather than just to pursue responsibility, increase pressure.

4. too large a task

Problem: The task cannot be moved because it is not finished. Two days in a row may not move.

Resolution: Split tasks, if not moved every day, will increase the psychological pressure, creating frustration. Splitting a task can resolve this part of the problem.

5. Too much rework

Problem: Because there is no clear definition of completion, so just developed, without testing the task, it is directly said to complete. Cause late rework, and re-take the time to change the previous bug.

Resolution: Clear completion of the definition of the team to reach a consensus. Our definition of the character is: After the developer's own test and another development of the cross-test (specific in the previous article is said). The task is completed before it can be moved to completion. This makes it necessary for developers to have their own tests complete, without problems. It also solves the problem that developers are reluctant to test.

Progressive Agility-Daily meetings