Daily Scrum this event is also known as a standard. I usually imagines a board where to reflect in their progress towards the sprint goal. So that's why we have the following picture here. So let's talk more about these event. As a typical characteristic of daily Scrum, we went over the fall, the first things that the eloquent team should attend this event on a regular basis and entire development. The second thing is that daily Scrum is not prescribed in terms of approach or flows that have to be used during this event.

But of course, it's very popular to refer to strong winds which suggest to use the fallen flow where each member or respond to three questions is the first one. What did they do yesterday? What I will do today and do I see any impediments that may prevent him from original sprint The goal so far is the beginning. And for the reference, I felt free to stick to these three questions. And finally, daily Scrum was internal event or development team. So West could visit this one.

But they should stay silent. How let's talk about truth statements in regard to the event, the statements which are correct and which are related to this event. So the first one is that daily Scrum is time boxed event, and 10 books to 15 minutes. And it's no matter whether you have three members on your team or nine members, you should always try to stick to this time box of 15 minutes. So that's important. And that's absolutely true.

It's absolutely true that Scrum Master and product owner could skip this event. So this event for the development team and if there is no Scrum Master, if there is no product owner, that's absolutely fine. He's through the daily scrumptious hell at the same place and same time. Yes, that's correct. And the reason is very simple because consistency reduces the complexity. So that was major statements which are true in regards to the daily Scrum or stand up.

Now let's talk about incorrect or false statement about this event is false the development team members to report to Scrum Master product owner on the daily Scrum so even if product owner and Scrum Master presented on the event, this event is internal. So, team members, members of development team practically should never work to Scrum Master or product on their own. They're reporting to other team members. It's false statements that structure of daily Scrum is well defined. So we already discussed this a little. We can of course use your Reference according to the scrum guide, and use three major equation, what do they do yesterday?

What I'm going to do today? And do I see any problems or impediments? Of course, we could stick to this approach. But once again, this meeting could be customized. It's false statements that members of the world when teams should stand on the daily Scrum or stand up. So daily Scrum is, I would say, canonical name of this event, but sometimes it's also called as a stand up.

And because of that, many people think that it's necessary to stand fair fairly as the nature of the round stand up. is very, it's very likely say as this amount should be actually maintained in stemmed way so people should stand. But in fact, development team should decide by themselves. So it's up to development team, whether they would like to stand or sit. So that was a huge are over you all is a daily Scrum or stand up event. And this event is considered as an opportunity to inspect and adopting Scrum.

Now let's move on and let's discuss other Scrum events.