Cfrgtkky

Is the scrum meeting started by the person whom comes to the meeting last

or

Anybody chosen by the team starts the scrum meeting?

Tried to find answer to this question but no luck till now

The team should decide. The meeting belongs to the team.

If the issue of starting off is a persistent problem during the sprint, then the SM should bring it up during the retro and facilitate the discussion to come to an agreement.

As there is no special meaning to who goes first and who goes after, team members should volunteer. If multiple team members volunteer it should take seconds to sort it out because it does not really matter.

If nobody volunteers you need to speak with your team about their commitment to this project and team. It is in their own self interest that someone starts the meeting on time.

The quesion looks the same with PSMI exam, one of my colleagues showed to me last month and got consultant from me. Some ideas for you, the practice base on my experience, you should consider the team's maturity to choose a appropriate way:

1. If you want to encourage your team member join the daily meeting on time, the meeting could start by person whom comes to the meeting last.


2. If your team use token as sign, who own token will start first.


3. Or Scrum master decide who will start (No recomend).

Please share your ideas, I think we have no answer for the type of question, just best practice.

Once everyone arrives – and they should be reminded to always show up on time – "just flip a coin, or roll a couple of dice." Or, if someone feels that they have a point that needs to be brought up early and wants to go first, let them.

nvoigt, I think there can be a meaning to whom starts first or make the daily scrum more effective depending on the state of the project. Some advise I can give to decide on a methodology goes as follows:

• Everyone should start at least once every certain time


• The order should be beneficial for the current state of the project (for example, it might make sense to naturally allow individuals working on close tasks to report one after the other to understand the big picture)


• When working on a “Crysis” or very “important” issues, it might be wise to allow those individuals to go first, so that the following individuals know if there’s any change they have to make to their activities during the day, this also allows the team to focus on getting done what is crucial at this point in time


• Important to the previous point: everyone should take important / critical tasks once in a while depending on circumstances


• I agree that the team should feel safe about being the first to do the daily scrum, so perhaps when whom starts is not important, you can try a random way to select who starts