2 ms·
I sometimes give two estimations in one: up-front cost of development and long term consequences. Could be something like, "8 points + three support cases per
by kqr 7y ago
I sometimes give two estimations in one: up-front cost of development and long term consequences. Could be something like,
"8 points + three support cases per week" for making a new feature without fully thinking it through.
Or
"32 points + misconfigurations every other month" for including a complicated feature that can more easily be abused.
Or
"We can go with our current best guess, and the effort of that is maybe 2 points + potentially 12 points later if it turns out we were wrong. Contrast this with 6 points to be certain of doing the right thing now."
In my experience, this is highly appreciated in environments that take you seriously, listen to you, and understand what "estimation" means,
- gvjddbnvdrbv 7y agoYour competition gave an estimate of 2 points, did the work, got paid and moved on. Now you are supporting the feature...
- kqr 7y agoIf that was the right call, then great! If not, hopefully someone learned from their mistake. If nobody did, I'm probably not interested in that business anyway; it sounds like it is a recurring source of friction.