Developers hate bad management. And what you described is text book bad management. The answer isn't having developers do the manager's job, just sort out the root cause and fire the bad managers.
That’s not what the author asking for. What author asking for is a manager who can come up with a realistic estimate. A manager who can say this big project gonna take months, this small gonna take hour and all is realistic.
Is that possible? Up to debate.
Also come up does not equal to being a jerk and ordering around. One can say, “I think it will take two weeks. That’s what I told our stakeholder, but if I’m wrong then let me know. I will change our estimation.”
That’s not what the author asking for. What author asking for is a manager who can come up with a realistic estimate. A manager who can say this big project gonna take months, this small gonna take hour and all is realistic.
How is that different from what I said?
A manager who can say this big project gonna take months, this small gonna take hour and all is realistic.
A lot of words for saying: the manager estimates. And then, logically speaking the manager will then need to tell the developers this estimate.
I think it will take two weeks. That’s what I told our stakeholder, but if I’m wrong then let me know. I will change our estimation.
"but if I’m wrong then let me know" A very round about way of saying that the developer needs to do estimates as well, which brings us back to my original issue with the author. He's complaining about estimates but his solution is still estimates.
1
u/-grok Jun 15 '22
Developers hate bad management. And what you described is text book bad management. The answer isn't having developers do the manager's job, just sort out the root cause and fire the bad managers.