DEV Community

loading...

Discussion on: 4 lessons I learned as a starting Scrum master

Collapse
technoglot profile image
Amelia Vieira Rosado ๐Ÿฃโœจ

In my nature is being a peace keeper, but when I resolved conflicts before they really started, I took away the chance of the team to overcome them, learn from them and become closer as a team.

This really spoke to me! I usually avoid conflict at all cost, but I have come to accept it and welcome it. ๐Ÿ˜Š

By the way, I've seen Scrum Masters being part time devs, and I can tell it does not work well. But when you have small teams, you are made to believe it is a "luxury" to have the SM be a fulltime SM. I personally prefer for those in managing roles to focus on that alone and stay away from developing. I don't believe in "multitasking". If you narrow down your focus, you are more likely to get better results that way (in my experience, at least ๐Ÿ˜…)

On another note...I loved reading this blog! I found it very insightful, so thanks for sharing! ๐Ÿ™‡๐Ÿปโ€โ™€๏ธ

Collapse
smeetsmeister profile image
Jelle Smeets Author

Glad that you enjoyed reading it!

I totally understand the luxury point you mentioned! Having been a SM of just a team of 3 for a while. What so you think about a SM having multiple teams?

Collapse
technoglot profile image
Amelia Vieira Rosado ๐Ÿฃโœจ

What so you think about a SM having multiple teams?

Hmm, I'm not sure how to feel about that. I think if the SM is a fulltime SM across multiple teams, it could perhaps work out. Though it may be taxing for the SM and will require more effort and proper planning in order to better manage the various teams. It doesn't sound very ideal, but it could be done. ๐Ÿค” How exactly, remains the question.

What about you? Do you see this working out somehow?