55 votesFilip Beslic commented
Remember that scrum is a 'project' methodology. The purpose of a project is to fulfil a goal. In order for decision-makers to be able to make the trade-off between project A & project B, they still need some sort of estimate (transparancy).
I think you are confusing scrum with scrum-ban. For a service team, monitoring WIP is sufficient. But when you are doing projects, decision-makers need at all times to be able to decide: “does the project still make sense” (transparancy)? Is the ROI still positive? You can’t achieve that without any type of estimation.
Since scrum is result-orientated and focussed on business-value, thus user-stories, the only correct approach is to estimate user-stories. In addition, next to the ROI, decision-makers need transparency to make decisions: when to schedule training etc.. They thus need to know approximately when functionality will be delivered. Hence you need estimations.
Another benefit; business-value is not the only factor which determines the PO’s priority decision. He/she can also take into account the complexity of a story.
3 votesFilip Beslic commented
I agree with Marc Trudeau on this one. I wouldn't enforce this, besides teams might come up with better techniques to be more productive in delivering business value.