Some time ago I heard about a trend of “No Estimates” and, have to admit, was not happy about it. The reason I wasn’t happy about it had nothing to do with understanding the velocity of a team. It had everything to do with the team missing out on critical conversations that occur when arriving at an agreed upon estimate. I love watching new teams estimate stories. When someone throws a 20 and someone else has a 5, the discussion that takes place – THE LEARNING – is pretty powerful to observe. Estimating is a way for team members to get to know one another better and understand how they each view things differently. Eventually, they start applying others’ perspectives to their own and the team truly finds a voice as a single entity.
Dan Mezick wrote a good blog post recently and pointed out “One may say with some certainty that the estimation task is actually a ‘cover story’ for the wider task of team learning. If estimates are 100% eliminated, how is this team learning replaced? Team learning is obviously essential. Discussions during the estimation task create many team-learning moments.”
Frankly, I believe a team, who is committed, will get to a point where estimates are not required. This will happen once they learn – not before. Scrum has estimates and the concept of velocity there for a reason. A team must go through Shu (Follow the rule) before they can muck around with it and find something else that works best for them or reach a state of Ri (Make the rule). If you start a team out with no estimates, I believe the learning curve and reaching a performing state will be delayed.
Some teams use relative estimation. Others will use Planning Poker. Heck, I have seen a team estimate in “farm terms”. Seriously. A duck is less than a cow which is less than a barn and so on…. It worked for them. Who am I to question it? So, yeah, maybe this idea has merit but, I really would caution against giving it a go with a newly formed team. Sound snippets like this one make me a little nervous. You can’t place a value on the conversation that takes place during estimation. You CAN place a value on a team taking twice as long to reach a performing state.