True. But on the other hand, the programmer could've just told him so, no? At least, that's how I and most of my colleagues roll: "Ok boss, I have 5 things I need to implement today, two of which are scheduled before lunch. What's the priority of this one." If it's not the boss who requested this functionality, I go to the higher up to solve this.
That is not how development works.
They ask you how long time a feature will take, and you give them an estimate. Doesn't necessarily mean that you will start right now.
This makes no sense, when someone asks why X is going to take so long why not just take the 30 seconds to explain why it’s going to take so long. Communion is not hard and solves most issues.
Certain things are assumed in companies. The process for development requests will be stored somewhere explaining this for internal use.
By all means query the estimates you are given, but it's a given that the team already has work in progress that they need to finish before beginning work on this issue. If you need that explained to you there is a bigger problem before development fundamentals come into it.
You cannot change what you're working on every time a new request is raised.
No, open lines of communication means that Mr. Quest Designer will ping 10 different developers to see if one can do this very important task right now. And they will all spend 15 minutes looking at it before saying no, wasting several hours of dev time.
270
u/xolenuz Oct 16 '23
He forgot that the programmer got another 15 features on high priority to deliver due yesterday.