3 ms·
Sounds like you should try really hard to: 1) Not hire someone that is going to argue about every single decision 2) Fire them if you get to the case of 1. I
by brianwawok 9y ago
Sounds like you should try really hard to:
1) Not hire someone that is going to argue about every single decision
2) Fire them if you get to the case of 1.
I have worked with quite a few "arguers" in my day. They all made good points. I am sure they were often right. But when it was 1v5 on the team for a particular decision, and our scrum master was making us having meetings for hours to resolve a stylistic difference that only 1 person agreed with.. blah. I cannot think of a better way to kill morale of an otherwise good team.
Sure in an ideal world, the team would work together and make decisions. If it's not working and one guy is sticking out over and over.. it's time to cut your losses. I have never seen a construction crew where one bricklayer would refuse to lay bricks a certain way, because he read a blog that another way is better. Sometimes you just need to put your head down and do the task, not make an argument about it.
- Avernar 9y ago> scrum master Your development process is based on micro management... > hours to resolve a stylistic difference so it's not surprising that there are debates about the one thing the devs have control over.
- brianwawok 9y agoYa right, which is why I don't think in my own company I could ever see hiring a scrum master. I get the point in theory, and I have met a bunch of really great guys... but the process is just too much for my taste.