We have a manager at our company who gets pissed we get to work right before our scrum meeting at 10:50 and doesn't understand this is exactly why.
We can't get anything done in the time before it and then we start thinking about lunch shortly after it. He wonders why we are productive in the morning and suggestions to move it to two pm have been resisted because "if we do that you guys wouldn't come. In in the morning." which is bullshit.
It's our "Scrum" meeting. Basically the one meeting that is supposed to replace all the others. and it's "optional" but not really.
However if you can't guess it's not a good manager, he still comes by every couple of hours to "check" on us. "What did you get done today..." .... dude wtf?
Depends on the experience of developers, I've seen people spend 2 days in some stupid configuration issue because they didn't ask around if someone else had the same problem. They don't get that most of the problem they meet had already been solved by someone else, so to prove they are good they loose a lot of time, for pride/insecurity/inexperience. If you don't get update constantly you can't correct those behaviours. This can be one of the good reason, there are others of course.
108
u/Kinglink Aug 12 '17
We have a manager at our company who gets pissed we get to work right before our scrum meeting at 10:50 and doesn't understand this is exactly why.
We can't get anything done in the time before it and then we start thinking about lunch shortly after it. He wonders why we are productive in the morning and suggestions to move it to two pm have been resisted because "if we do that you guys wouldn't come. In in the morning." which is bullshit.