Software engineer as a profession, frustrated musician as a hobby, casual sportsman and social drinker in my free time. My personal blog: https://mirdevs.com
The Scrum master only needs to make sure that the meeting takes place, but not necessarely attend. He can facilitate at the beginning if the members don't know how to do it: what i did yesterday, what i am going to do today and spot any blockers... Also foster the collaboration between members, and preventing that it becomes in a simple status report for a manager.
Why? Because a Scrum Master is not an administrative assistant of the process, "the person that just" creates the meetings or updates the board. The SM is a transitional figure, it helps the organization to swap from traditional planned, cascade, top-down organization,... to agile ogranizations with product teams. The SM is a promoter of agile/scrum and as the team improves, his impact fades away until it completely disappears because you already have a high-performant product team in the organization. Everything works well.
The Scrum master only needs to make sure that the meeting takes place, but not necessarely attend. He can facilitate at the beginning if the members don't know how to do it: what i did yesterday, what i am going to do today and spot any blockers... Also foster the collaboration between members, and preventing that it becomes in a simple status report for a manager.
Why? Because a Scrum Master is not an administrative assistant of the process, "the person that just" creates the meetings or updates the board. The SM is a transitional figure, it helps the organization to swap from traditional planned, cascade, top-down organization,... to agile ogranizations with product teams. The SM is a promoter of agile/scrum and as the team improves, his impact fades away until it completely disappears because you already have a high-performant product team in the organization. Everything works well.
Thank you for asking! :)