Agile and invincible is not just standing (18)

Not just standing (18) This article is from agile and invincible

In the evening, Seagate logged on to MSN and was ready to continue to discuss daily scrum standing meetings with agile sages because they spent a lot of time on this standing meeting. This is not only inefficient, but also has a lot of comments. Unfortunately, the agile sages are not online. A Jie had to go to the shrimp network to view his customized blog articles.
A Jie is watching the addiction, suddenly felt a screen shake, and then an MSN window popped up, A Jie cut over with a mouse to see, it turned out to be agile shengxian online.

Agile sages: Hi, A Jie.
A Jie: Hello! Sages.
Agile sages: Let's continue to talk about your last sprint experience. I remember you said it would take 40 to 40 days for the daily scrum "likes ~ 50 minutes, right?
A Jie: Yes. On the daily "likes" day, we were able to focus on time a few days ago and try to update enough relevant content. But in the future, things will not be marginal, and the time is too long. In the last few days, due to their busy schedule, the attention and attention to this meeting were significantly reduced.
Agile sages: Maybe you should change your mind.
A Jie's eyes lit up and replied immediately: Can I use e-mail instead?
Agile sages: absolutely no! E-mail cannot replace daily scrum meetings. E-mail only increases communication costs, and does not provide details or opportunities to ask questions to others, nor can it help other members solve problems.
A Jie: Can I leave it alone? We all think that meeting every day is of little significance!
Agile sages: This "Inaugural Meeting" will not only help everyone understand what others are doing, how the current project plan is going, but also help everyone solve problems that impede doing things and share promises. In fact, these are very helpful to improve the team spirit.
A Jie: Oh, But we spend so much time in meetings every day, which affects our work efficiency. Is there any tips to keep the meeting tight and effective?
Agile sages: I have a lot of tips and experience. I have summarized 8 articles. Do you want to hear it?
Ah Jie: Well, I'm waiting for you to teach me.
Agile sages: The first guiding principle is that the subject is clear and cannot be mixed with other irrelevant topics. To do this, you only need to ensure that each person only answers four questions.
A Jie: What are the problems?
Agile sages: "What did you do after the last meeting ?", This requires the entire team to have a good understanding of what the Member is doing and the current progress, but not to be overly detailed. Otherwise, most people will lose patience.
A Jie: Well, the last time someone said "the same as the last time", someone also said "I am changing a bug ". It also seems wrong.
Agile sages: Yes, "Details determine success or failure." You must pay attention to the details here. The next question is "How long is the remaining time for each task you are responsible ".
A Jie: We ignored this.
Agile sages: some teams do not discuss this topic during stand-up meetings because they use separate tools and software to track the remaining workload. If you have not asked each Member to take the initiative to update your Excel sheet before the meeting, you need to provide the latest estimates at the meeting. In scrum, it is very important to re-estimate tasks every day. In this way, you will know how much work you still have and whether you can complete it in the remaining time. If your estimation is insufficient and you feel that it cannot be completed, adjust the plan in time.
A Jie: It seems that if we stick to it, we also need to use a dedicated tool. What is the concept of adjustment? Did you take out the unfinished task?
Agile sages: this is a way of thinking. The other is to resolutely end the current sprint and start the next sprint again. But in any case, you should greet the product owner in advance to let him know your latest decision.
A Jie: OK. What is the third question?
Agile sages: "What do you want to do before our next meeting ?", When the work between members is dependent, this will give a good reminder to other members.
A Jie: set the goal for the day.
Agile sages: Well, the last question is, "Is your development blocked ?" This is the most important issue. The problem that hinders the development of a person will ultimately impede the entire development team. Therefore, we must encourage everyone to express their own problems. Once someone puts it up, as a scrum master, you are obligated to help him eliminate these obstacles as much as possible.
A Jie: ah? Some technical problems cannot be solved by our developers. I am not a technical expert.
Agile sage: For a scrum master, you do not have to solve the problem yourself. More importantly, you need to coordinate and schedule resources.
A Jie: Well, it's almost the same. It scared me to death. By the way, what should I do if I discuss technical issues during the meeting? This happened last time, and we had a long debate.
Agile sages: It's very simple, depending on the situation. If it is a few words of discussion, let it continue without interrupting it. In this way, the problem can be solved quickly and the effect will be good. If someone says too much details or is too far away from the question, as a scrum master, you have the full responsibility to interrupt them to ensure that the meeting is normal. If you need to discuss it in detail, remember to arrange a separate meeting after the meeting for special discussion.
A Jie: OK.
Agile sage: you also need to mention that the main purpose of daily scrum is to let each member promise what to do and discover obstacles in progress. In the past, we only emphasized "discovering obstacles in progress by ourselves" and ignored "what do we promise to do ". Why should we make each member promise what to do, rather than arrange the team leader? This principle is very simple. Everyone will take care of what they say. If things are arranged by others rather than voluntarily promised, some discounts may be made on the initiative, which will affect the progress and quality of things.
A Jie: absolutely agree!
Agile sages: second guiding principle: standing meetings only allow "Pigs" to speak, and "chicken" to speak.
A Jie: pig? Chicken? Why are there pigs and chickens in the standing meeting? What do you mean?
Agile sages: Well, in scrum, the scrum master and team are called "peigs-pig", while others are called "chickens-chicken". These titles stem from such a joke.
 
Chicken said: Hi, pig! What should I do if we open a restaurant?
Said pig: Oh, I don't know what we sell?
Chicken said: Ham and eggs ...... What?
Pig said: Forget it. I don't think so. I am fully engaged, but you are only involved!
A Jie: Haha! Interesting. I didn't expect many allusions in scrum!
Agile sages: The third guiding principle is that all people stand in a circle and cannot sit around a table. "Standing" implies that this will be very short, forcing everyone to focus more and invest more, and effectively avoiding people sitting and sending and receiving e-mail and other distractions.
A Jie: Got it.
Agile sages: Fourth guiding principle: ensure that the entire team participates in the daily scrum meeting. Everyone, developers, testers, and document writers, must attend and follow the meeting rules as long as they are "pig.
A Jie: this is not a big problem. All of us can ensure that we participate.
Agile sage: Guiding Principle 5: daily scrum standing meeting is a team exchange meeting, not a report meeting. Each participant should be clear that the development team is reporting and communicating with each other, rather than reporting to the product owner, manager, or scrum master.
A Jie: although this is irrelevant to the Conference efficiency, it is indeed worth noting.
Agile sage: Guiding Principle 6: daily scrum standing meetings should be controlled within 15 minutes. This does not need to be said.
Agile sage: Guiding Principle 7: Do not use daily scrum standing meetings as the beginning of a day.
A Jie: Well? What does this mean?
Agile sages: if you do this, some members do not want to do anything before opening a daily scrum meeting, this laziness is actually a damage to productivity. Therefore, do not start the meeting too early in the morning. Do not associate the day with the meeting. Of course, this meeting should not be too late. Generally, it is suitable for.
Agile sages: Eighth guiding principle: scrum standing meetings should be held at the same time every day. This not only gives the team a sense of standing meetings, but also anyone interested in your standing meetings, such as the product owner, other project managers, or department managers, you can come and hear it at any time.
A Jie: This is like a religious ceremony. What else?
Agile sage: after the meeting, the scrum master updates the remaining time of the projects in the sprint backlog that the development team members are responsible for, and records them in the drawing.
A Jie: Burn a drawing?
Agile sage: Sprint burndown chart in English. Let's take a look at a burning chart that we used to draw automatically in Excel.
 
A Jie: What is it mainly used?
Agile sage: it shows the amount of work that is left on a daily basis until the development team completes all tasks (calculated by hour or day ). Ideally, the parabolic track should be exposed to zero point on the last day of the sprint. This may happen sometimes, but not in most cases. What is important is that it reflects the actual progress of the team relative to their goals. Note that it is not the amount of time spent currently, which is not relevant for scrum, but the amount of work remaining-how far the development team is from completing the task. If the trajectory of this curve does not end at the end of the sprint, the development team should speed up or simplify and reduce its work content.
A Jie: Well, this chart is really useful and very intuitive, with a clear view of the project progress. You said this chart can also be managed using an Excel table?
Agile sage: Yes, I can provide you with a template, manage product backlog and sprint backlog at the same time, and automatically generate this burndown chart. However, many teams think that it is simpler and more effective to mark with drawings on the walls of their studios, and can be updated with a pen at any time. This less technical approach is faster and easier than workbooks, more visible. I suggest you do the same.
Ajie: OK! I think this standing meeting should be fully discussed. Let's discuss the product demonstration and review? I don't want to screw them up.
Agile sages: Let's talk to you next time! There are more things to talk about than the daily briefing.
A Jie: That's all right! When? It's not too late. I want to present and review sprint2 products!
Agile sages: Well, it must have been before. I also said it's not good! Next weekend! I was not that busy at that time.
A Jie: Good! I am always waiting for you! 886!
Agile sage: 886!

A Jie decided to organize a daily scrum rule according to the advice of agile sages. So while the "things" in my mind are still there, I opened my blog and wrote the following text.