|
|
|
|
|
|
by jph
1502 days ago
|
|
|
The best estimation tactic I've found in practice is ROPE, which works because it helps different kinds of stakeholders understand different kinds of estimates and ranges. R = Realistic estimate. Based on work being typical, reasonable, plausible, and usual. O = Optimistic estimate. Based on work turning out to be notably easy, or fast, or lucky. P = Pessimistic estimate. Based on work turning out to be notably hard, or slow, or unlucky. E = Equilibristic estimate. Based on 50% probability suitable for critical chains and simulations. https://github.com/sixarm/rope-estimate |
|
|
The issue I've had is that most "stakeholders" just want it boiled down to one number and don't care about any nuance. If I say it will take 2-4 weeks, they will assume 2 weeks if it's convenient. If there's a list of tasks, they will add up the lower bound of each task and discard anything they don't deem necessary.
It seems to me that any estimation tactic works well if you assume fair intent.