In Twitter, we use the convention of “hashtags” to connect a tweet with a theme or topic so that it is easy (or at least a bit easier) to search and find tweets for topics we want to follow.
Several people have blamed me for coining the “#NoEstimates” hashtag. It might be true – I’m not sure. It is possible that I was the first to use this hashtag for Software Development – a search of Twitter history on it shows that, as far as I can tell.
[UPDATE: I found the following post from Aslak Hellesøy - @aslak_hellesoy dated Feb 10, 2010 that used this hashtag
@obie at #speakerconf: "Velocity is important for budgeting". Disagree. Measuring cycle time is a richer metric. #kanban #noestimates.]
SO… What is the Topic of the #NoEstimates Hashtag?
Here it is, as defined by ME. Others probably have their own idea:
#NoEstimates is a hashtag for the topic of exploring alternatives to estimates for making decisions in software development. That is, ways to make decisions with “No Estimates”.
I’ll probably modify this a bit over time – I put this together quickly as a starting point.
Also, A Word About Estimates
Estimates are typically and pervasively used in the decision-making process throughout software development organizations and efforts – both in ”phased/waterfall” and “Agile” methodologies. They are ubiquitous – it is rare to find a project/organization/effort where it isn’t simply accepted that “we must have estimates – it is the only way”.
Additionally, for a long time I’ve been noticing that almost every training, book, conference session, article, or blog on “Agile” software development has a very heavy focus on estimating. I’m fine with important things taking a lot of our attention – they are important, after all. Are estimates that important?
I’ve also noticed over the years that many organizations have a number of dysfunctions in how estimates are handled, and the overall decision making process that depends on estimates. Have you noticed any dysfunctions?
So… I started doing “5 why sessions” or similar exercises at conferences and user groups, and other investigations into the reasons for this, and the dysfunctions that people have been experiencing. I also started discussing alternative ways to manage software development efforts without using estimates. I’ve been working without estimates for years for many decisions that are typically “estimate-driven” in software development management, and some people are interested in how to do this.
It’s important to ask ourselves questions such as: Do we really need estimates? Are they really that important? Are there options? Are there other ways to do things? Are there BETTER ways to do thing?
If we are willing to simply play the “devil’s advocate”, and imagine (or at least temporarily pretend) that perhaps there are better ways to make decisions, it can lead to more open thinking and clarity as to why we “believe the things we believe”. Why not question the things we hold so dearly?
There ya go! Have Fun!