2 ms·
Nope, waste of time. In the true spirit of Lean, eliminate waste - the wasteful time of estimating things and the overhead of that. When using kanban flow inst
by matt_s 5y ago
Nope, waste of time.
In the true spirit of Lean, eliminate waste - the wasteful time of estimating things and the overhead of that. When using kanban flow instead of sprints it really doesn't matter what any estimate is.
This smells like someone above is asking when they can have something done so people in the middle have to come up with something.
Maybe the team lead/mgr can test doing the estimating themselves and letting the team just do the work. If you've committed to a feature or fixing a bug and it takes longer or shorter does it matter?
- thiht 5y ago> If you've committed to a feature or fixing a bug and it takes longer or shorter does it matter? It's not, but it's still nice to get a rough estimate, isn't it? It's also useful when you need to prioritize things, because you often cannot fix all bugs or implement every nice to have feature. It can also be interesting to find out why a feature estimated to say 3 points took a whole sprint to be implemented: is there tech debt? was it badly specified? maybe even the dev would have needed help (pair programming, formation, etc.) but didn't ask for it? It's useful for self improvement
- volkk 5y agoi dont disagree but then comes the question -- how can product effectively create a roadmap without any estimates? which then brings me to the question of whether roadmaps are a waste of time? but senior leadership needs to understand priorities and what the company will be addressing in the next quarter. so it always folds right back into -- we need to create estimates even if they're completely wrong which seems stupid and insane