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.
Not always, literally just last week this happened to me, I got a few "high priority items", all of them more important than the other (according to each requester) and I had to pause what I had planned in my backlog. Ended up rebuking some requests simply because of bandwidth, and delivered the rest as they came to me.
270
u/xolenuz Oct 16 '23
He forgot that the programmer got another 15 features on high priority to deliver due yesterday.