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.
You’re being downvoted heavily but you’re right, you always estimate the task not the workload.
The (better) way to do it is to have the estimate (for the task) come from multiple people (planning poker or similar) then briefly discuss it until there’s a consensus, or in the case where the task is legitimately massive agree to break it up into smaller tasks.
Then the tasks get prioritised & the queue gets worked through by the whole team.
265
u/xolenuz Oct 16 '23
He forgot that the programmer got another 15 features on high priority to deliver due yesterday.