“Whenever you’re thinking high level, someone will bring you down to earth and ask you to get into the weeds. Whenever you’re in the weeds, someone will complain that you’re not being high level enough. It’s the burden we bear. Just when you think you’ve figured things out, you’ll encounter a person who needs to see your roadmap, or backlog, or “sprint backlog”, or “project”, or “plan” in a whole new way. So…changing delivery based on context is important. You could argue that it is the biggest challenge facing PMs. It is a design problem!” “11 Ways I Visualize Product Development Work” @johncutlefish
found at Twitter (@duarte_vasco)
“In the Agile world, there’s an effort to move away from estimates in hours towards estimating in story points, often using a Fibonacci sequence. The idea is that the larger a story is, the more uncertainty there will be around it and the estimates will be more inaccurate. The approach underscores the uncertainty in every estimate.”
Uncertainty is something we try to avoid – whenever possible. We want to know what we need to know, to be able to come up with reliable plans. Plans are supposed to keep deviations away from us, as they could make us struggle. Uncertainty can be seen to impose scepticism, doubt, mistrust. But it is always there and cannot be neglected, so we should anticipate it in favor of more robust plans.