I also never heard from people, that they are fond of SM giving space and encouraging them.
People want to be part of something great and valuable, have a freedom for their ideas, and not work long nights to fix bugs. And from my point of view business and dev teams are enablers for this.

Correct more tools than culture. But if we want to be efficient, which I think part of every modern team culture, we need these tools. And leader can use this tools to build culture. Not only encourage.
And this is the difference from my point of view.

The thing is that it is not clear. Adding ci/cd is measurable. It now takes us xvtimes faster to deploy feature, so cycle time is y times less.
Giving methods and space is not measurable. It might be helpful, might be not, but the question is how to measure this?

Exactly. These SMs are just guided by SCRUM. And this why you should be dev to build culture, you can’t be aside.
You should teach the team: ci/cd, sec shift-left, unit tests, don’t be afraid to chat in PRs, team chats, calls, name it.
This helps to build culture, not 15 minute daily standups.

On dev level I wouldn’t do it. I agree with you that it is hard. I’m not Elin Mask to measure value on LOC:-)
But on dev team level:
- number of stories(pbi) delivered within sprint
- cycle time for delivery
For PO:
- user engagement, e.g MAU, user attrition rate
- revenue (maybe, not sure)

Exactly. These teams are self-organized in terms of SCRUM. And my point is that most devs now days are well-trained and stick to protocol to do agile w/o SM. The industry is matured in terms of how to do SCRUM.

I’m working with a lot of teams as a tech consultant for years. All that teams use agile approach. The one thing I noticed that the effectiveness of the team doesn’t correlate with ceremonies and time-boxing. But it correlates with team culture. What does team value, how good communication is.

Again how to measure giving space and methods? Describe typical SM day?

Surgers and austranauts don’t need SMs because they are self-organized and effective. The same for devs. Maybe in early SCRUM years we needed SM. But not in 2023.

Because if devs are specialists, not SM, how does SM know what is right and what is not.
Why we don’t have SM for surgery team? Austranauts maybe?

If you dev it doesn’t mean you should be busy with the code all time. You can lead.

I beg to differ. SM-dev should plan their time to educate, organize, etc.

SM that not involved into contribution doesn’t provide any value. Since the goal is not establish all ceremonies and time boxing.

The goal is to create self-organizing team. And this is impossible without hands-on.

The team makes value. Value of PO and devs can be measured. Value of SCRUM Master is not that straightforward. Especially if we have self-organized team.

Exactly as you described. From devs to devs. SCRUM Master is a role for dev, not a job.

Only if you contribute (anything that add value and measurable) you have enough context and power to decide what is “waste” and what is not.

Ok. I agree that there are inexperienced in SCRUM teams and SCRUM Master may help. But still why SCRUM Master decides that this is the better way than “we always done this way”.

My point is the team should decide how long is daily, do they need ceremonies, or SCRUM at all. Not SCRUM Master.