If you've developed software for even a few years, you know estimates are basically worthless.
Unless you're estimating old technology, and building something trivial - the company's asking you to commit to something you've never done before.
I've heard the statement before that being an "agile" team or company is only possible if it's accepted from the leadership all the way down to the individual developers in a company.
The hardest part about being agile is that we still find out we're wrong, and even more frequently!
The question is: how do people treat each other when they're wrong?
Click below for the full interview with Scott Nimrod.
Or listen as a podcast: