You're assuming that the individual's labour is the only input into work completion.
I think those questions are good. One benefit is that it can reveal potential organisation-wide blockers:
*Getting design changes could be slow (and hence the design department may be understaffed, or inefficient communication channels)
*Maybe some processes can be ran in parallel. Someone can build the login form while the other does the database.
*They might require git access for another department that could take a while to come through.
Considering engineers' time is often the greatest cost for a technology startup, you can bet they'd be incentivised to maximise the efficiency of it.
Not only might they reveal potential blockers, but answering it also helps both parties understand they're on the same page regarding what the task entails. If the task is building a login form and the response is 'It will take two days to train the neural network', you can nip that in the bud.
I think those questions are good. One benefit is that it can reveal potential organisation-wide blockers:
*Getting design changes could be slow (and hence the design department may be understaffed, or inefficient communication channels)
*Maybe some processes can be ran in parallel. Someone can build the login form while the other does the database.
*They might require git access for another department that could take a while to come through.
Considering engineers' time is often the greatest cost for a technology startup, you can bet they'd be incentivised to maximise the efficiency of it.
Not only might they reveal potential blockers, but answering it also helps both parties understand they're on the same page regarding what the task entails. If the task is building a login form and the response is 'It will take two days to train the neural network', you can nip that in the bud.