Estimates are difficult for developers and product owners
Product Owner: Hey, how long do you believe Feature F will take? Developer: Idk. We haven’t even started working on it and it’s bound to stir up some old issues. Estimates come in various disguises, but when you peek under the trench coat there is always the question: “How long — and using what amount of resources — will be required to do X?” When I wear the developer hat, it can be infuriating to attempt to give an answer. It’s difficult to estimate (or the product owner could do it themselves) and a lot of the time it can be difficult to see why the estimate is even important. When I wear the product owner hat, estimates are a crucial piece of the puzzle that must be laid in an attempt to plan the short and long term life cycle of a product. In this post I want to…
