Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
pmso26510dIt makes sense, but they also need to do their homework.
They can't simply say: I want that the system can track boxes in trucks and warehouses.
They need to specify what they want to happen if a box is stolen from a truck, for example.
Voxera884210dWhen we get question on time we have the option to specify either unknown if we judge there are to much undefined, or to large if we determine that the scope is to big for a guess and the uncertainty would be to much.
In both cases it will need to be broken down into smaller tasks before a time estimate will be done.
eo287578610dHappens to us all the time. The worst thing is, let's say the devs said
"so these will take 2 weeks. We know nothing about library XYZ so it could take from 1 week to a month... we're not sure."
What management hears:
"2 weeks + 1 weeks tops, maybe less if we're not being lazy"
PepeTheFrog29810d@Voxera yeah trying to break down, doing more research and design the work in modules is what I usually do and also what I started doing initially, but I have been told to bundle everything vaguely in huge tasks.
I know from experience doing huge estimates with no information never works and I have warned the estimates will be insanely innacurate or quite possibly underestimated, but management does not seem to care. It also seems I'm forced to fit my estimates to what management wish to have.
It's just frustrating to be forced to do botched work when you have time to do it properly.