I am myself a Scrum Product Owner and Project Manager and I am one of the very view Product Owners who can code. And I know a lot of Scrum Masters who cannot write a single line of code, even do not understand what a variable is.
For me, a Scrum Master is a coach and the main task is to ensure, that the scrum process flows and the scrum team can work without impediments. And most impediments are not of technical nature I think, but more a problem of processes, psychology, social components and over all wrong business objectives. Of course it depends heavily on the individual situation, of the team and the company, but in most cases, technical skills are not required for a Scrum Master in my eyes.
But anyway, I think Scrum is not the only key to improve software development. In my eyes, interdisziplinarity is more important and pretty underrated. In publishing companies there are sometimes job descriptions like "editorial-dev" and the task of this job-holder is to mediate between editors and devs. Not the topic of this post, I know, but I would always vote for interdisciplinary teams of devs and non-devs and more communication between them ...
Yes, I share some scepticism about Scrum as the cure for all evils, but let's put that aside for the purposes of this post. In fact, one of the other takeaways from that course was that given a sufficiently effective team, the much-debated differences between competing "Agile" methodologies don't really amount to much.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good point, but for me, this seems pretty normal.
I am myself a Scrum Product Owner and Project Manager and I am one of the very view Product Owners who can code. And I know a lot of Scrum Masters who cannot write a single line of code, even do not understand what a variable is.
For me, a Scrum Master is a coach and the main task is to ensure, that the scrum process flows and the scrum team can work without impediments. And most impediments are not of technical nature I think, but more a problem of processes, psychology, social components and over all wrong business objectives. Of course it depends heavily on the individual situation, of the team and the company, but in most cases, technical skills are not required for a Scrum Master in my eyes.
But anyway, I think Scrum is not the only key to improve software development. In my eyes, interdisziplinarity is more important and pretty underrated. In publishing companies there are sometimes job descriptions like "editorial-dev" and the task of this job-holder is to mediate between editors and devs. Not the topic of this post, I know, but I would always vote for interdisciplinary teams of devs and non-devs and more communication between them ...
Yes, I share some scepticism about Scrum as the cure for all evils, but let's put that aside for the purposes of this post. In fact, one of the other takeaways from that course was that given a sufficiently effective team, the much-debated differences between competing "Agile" methodologies don't really amount to much.