I don't understand your hostility. Are my opinions hostile to you? I'm sorry if they were. I'm just sharing what I've learned.
> Wow, that means...literally every dev can be a scrum master.
Yes. And that's why if you take the training as a developer, you get "Certified Scrum Master" training. If you would stop trying to gotcha me, you would see this is an potential area of agreement between us.
I don't think you have a proper sense for what a 'blocker' is in the context of Scrum. In a normal workplace and well-functioning team, blockers are few and far between so the SM shouldn't need to engage all that often anyways.
Not all problems we encounter in the workplace are in code. Scrum has roles to own and manage the different kinds of problems. Scrum is also a flat hierarchy, it's fairly minimal. You're supposed to make things as simple as possible, but no simpler. I think you're over-simplifying.
The 'Business' is capitalized because of English, but feel free to read my words with business all lowercase. I don't worship any man, bad look.
Product Owners need to be subject matter experts or at least SME's in training. In my experience lead developers who try to also wear the PO hat sometimes have trouble getting their heads out of the minutae. If you have seen the opposite in your experience, then lucky you.
> Wanna hear about my revolutionary idea? A development team consisting of...developers.
When you get to know types of folks other than coders, you get to appreciate how they make important contributions to the project. I think you were trying to smash home a point here, but the world is bigger and more interesting than what you wish it was.
> Wow, that means...literally every dev can be a scrum master.
Yes. And that's why if you take the training as a developer, you get "Certified Scrum Master" training. If you would stop trying to gotcha me, you would see this is an potential area of agreement between us.
I don't think you have a proper sense for what a 'blocker' is in the context of Scrum. In a normal workplace and well-functioning team, blockers are few and far between so the SM shouldn't need to engage all that often anyways.
Not all problems we encounter in the workplace are in code. Scrum has roles to own and manage the different kinds of problems. Scrum is also a flat hierarchy, it's fairly minimal. You're supposed to make things as simple as possible, but no simpler. I think you're over-simplifying.
The 'Business' is capitalized because of English, but feel free to read my words with business all lowercase. I don't worship any man, bad look.
Product Owners need to be subject matter experts or at least SME's in training. In my experience lead developers who try to also wear the PO hat sometimes have trouble getting their heads out of the minutae. If you have seen the opposite in your experience, then lucky you.
> Wanna hear about my revolutionary idea? A development team consisting of...developers.
When you get to know types of folks other than coders, you get to appreciate how they make important contributions to the project. I think you were trying to smash home a point here, but the world is bigger and more interesting than what you wish it was.