Earlier quoted context omitted.
Would you feel it fair, when you require an estimate, to have to say what decision you'll make with it? Usually, when someone insists on getting estimates, that's my way to make sure that they really need it. besides, it also helps making an estimate that won't be useless in the context of the decision to be made. The lesson I learned from asking that is 1) many people ask for estimates without a clue about what they…
I’m talking about particular user stories, not the overall estimate. For projects it’s almost always a budget issue “how much money and time does it need?” And that’s important because, like money is hard to get and $1 is different than $2M. I think the time is usually related to money due to revenue and costs and whatnot. My example was about estimating “how long to add a revert button to 5 pages” and that requires…
I've never been in a situation where adding db crud was its own user story. Usually, we group this and the button (and the metrics necessary to trask feature use) in a single item, and pair people so it can be shipped in one go.