What useful recipes do you know for holding Stand-up rallies?

Question

Agile

Actually, there was a desire to hold stand-up rallies. I would like to hear advice from experienced people on this topic. What is the best way to do it, what subtleties are there, etc.?

Now 2 questions are tormenting: to hold rallies for the whole team or on a project basis, if a person is working on several projects? What questions to raise? What is the best way to organize the process? What to pay attention to?

I would appreciate any advice and stories. I want more bad stories and bad experiences.

Thanks in advance.

Answer 1

If there are no more than five of you, hold a general one. If much more - spend on projects. So it will be easier for you and people will not be at the rally for a long time. I spent twice a day: what will be done, what is done. So that people do not remember in the morning about “what happened”. The rally should be as short as possible. Very often it can happen that this will slide into a discussion - it must be stopped.

Answer 2

> hold rallies for the whole team or according to the project
Depends on the size of the team. More than 7-8 people - already stressful. Well, 10 is the maximum. If more, then it is better to break it into 2 parts, each of which is stand-up separately, and once a week - one big “stand-up of stand-ups”.
>if a person works on several projects?
Then he needs to participate in stand-ups of several teams, because the essence of stand-ups is for the team to roughly imagine what each of its members is working on.
In general, everything is according to the book: three questions “1) what did I do yesterday, 2) what will I do (or better, what am I going to achieve) today, 3) are there any difficulties.”
As for the difficulties, you need to be very careful, not falling into details, otherwise the stand-up will develop into a spontaneous rally to solve this problem. The best option is to quickly find out what kind of difficulty the person has and determine who can help him with this. Then they meet right after the stand-up and solve the problem. Why right after the stand-up - because the one who can help is already distracted, so he can help right now. If you let him sit down, then he will begin to get involved in the work, he will need to be distracted, he can say “come on in half an hour”, and for this half an hour the one who has a problem will either sit stupidly and do nothing, or climb on Habr, as a result, the solution to the problem will be delayed not even for half an hour, but for a couple of hours.
You definitely need a “leader” - someone who follows the rules so that all 3 questions are answered and does not allow you to fall into details. It's good practice to let each member of the team lead (for example, this week one, next week the second, and so on). After you stay in this skin, somehow by itself it turns out to follow the rules much more clearly :)
And, well, the time of the event. The sooner the better, because if the stand-up is in the middle of the day, then “what I did yesterday” will be superimposed on “what I already did in the first half of the day”, and “what I am going to achieve today” will be spread over “this afternoon” and “tomorrow morning”, in as a result, the work will be postponed for “yes, fuck it, I’ll finish it tomorrow morning”, but how do we “know how” to correctly calculate the time - I think you don’t need to tell anyone :D

Answer 3

Всё уже насоветовали, придерживаться 3х вопросов считаю важным.
Добавлю еще что с одним скрам-мастером проводили стэндап с реальной стеной, с другим задачи были в олнайн-тулзе. И во втором варианте (когда все уже передвинуто еще вчера) во-первых довольно сложно порой вспомнить всё что сделано; во-2 (что самое неприятное) явно не видно ни прогресса, ни отсутствие его. Каждый вроде что-то делал/сделал, а реальные задачи (бумажки на стене) стоят на месте, не видно берут ли их вообще. Вообще важно не говорить что делал / буду делать, а надо: что сделал/что не сделал(почему)/что сделаю. Большая разница.
As for the question “what difficulties were there” - IMHO the wording is incorrect. In my opinion, it makes no sense to list the problems if you still completed it on time, there are eventually regular problems. But it makes sense to list / try to list when it is just obvious that you are failing with the deadline (a threat to the task and / or the entire sprint), it is especially necessary if it seems "that there are no problems. So there may be problems in lack of sleep, the problem is real, but rarely recognized as a problem (more often we look for problems outside)
Total questions should be 1) what did I do 2) what will I do 3) What threatens the sprint / deadlines

Answer 4

Stand-Up Daily Meeting - held as part of a team working on one project (the whole team must be present at the rally, regardless of the number of people).
Everything falls into place if you correctly formulate the goals of the Day Meeting a:
Possible meeting participants (it all depends on the composition of the team):
— Manager : has the most complete information about the planned tasks for the iteration;
After the rally: the manager must understand the "progress" on the tasks in order to understand what is left;
After the rally: the manager must understand who is free, propose a new task;
- Architect : has the most complete knowledge of architectural solutions in the project;
After the rally: must be aware of all the innovations adopted by the developers in solving problems;
- Tester : has information about the existing problems in the stabilized version;
After the rally: should represent the scope of the upcoming testing - completed tasks;
The “Report Format” must be set, it must be simple, but meaningful (a reporting culture must be developed);
There must be a moderator (most often a manager) who controls the reporting process and format;
The rally should be limited in time, depending on the number of people in the team (we have a team of 13 people, reports in 15 minutes);
Report format for developers :
- Task?What task(s) did you work on yesterday?
- Finished? Finished or not finished?
— Problems? Are there any problems or what tasks still remain (approximately how much time is needed)? Help
? Do you need help and what kind (discussion/colleague)? — Innovations? Are there any innovations that other developers need to know about? Reporting format for Testers: - Is the application ready for installation? — What critical problems have been found and need to be addressed? Example: - Andrey: yesterday he worked on the task "configuring the database replication on the Slave", the task was completed - he is ready to take on another task.


— Ivan: yesterday I worked on the task “commenting messages in the My Messages tool”, I didn’t finish the task, I didn’t have enough time, it remains to write tests and integrate, I plan to finish by lunch.
— Egor: yesterday I worked on the task “writing a Cheff recipe for installing a new application”, I didn’t finish the task, a number of technical problems arose, I would like to discuss it with Andrey after the rally.