4 ms·
Is this not what estimating and refinement means to developers? I’m always pulling a number out of my ass, but that number is generally informed by current and
by mynameisvlad 4y ago
Is this not what estimating and refinement means to developers? I’m always pulling a number out of my ass, but that number is generally informed by current and past work, unknowns, and a “gut feel”.
If that number is too high, then that’s a sign to management that the work needs to be changed. The only way to determine that is to estimate it then make that call.
- hgsgm 4y agoThat's relevant for order of magnitude only, and only for "body sbop" work that is the same as previous work. And only works if management wants an estimate. More commonly, management wants a lie they can tell the client.
- mynameisvlad 4y ago> and only for "body sbop" work that is the same as previous work. That’s absolutely preposterous. As a senior engineer, I have seen enough that I have at least a high-level idea of what most of the dev tasks and stories I’m estimating are. I don’t always have the specific details that may change the estimate, but I also have a whole team of other people who have seen even more things and can inform that opinion. The point of refinement sessions is to share this information with everyone else so an estimate can be created and if needed, tasks can be better defined, split up or merged. > And only works if management wants an estimate. More commonly, management wants a lie they can tell the client. Wat? Estimates is used for plenty of reasons that have nothing to do with external clients. How do you think your manager, their manager, etc knows what is going on and approximately how long it’s going to take? They’re going to be far more disconnected from the work than the people doing it day to day, so they would generally have no clue how long something is estimated to take without someone telling them.