We are doing a fair amount of estimating at work right now. We had a long meeting discussing an estimate for a project with heaps of unknowns. We put a decent plan in place for refining it next week on our own, but this book will help a lot I think.
I took a course at OMSE that covered a bit of estimating, but it was far too academic. I flipped through the book from the class I took and while it had some good ideas, it wasn't practical enough. McConnell's book touches on some of the academic approaches, but is very concise and has heaps of practical advise. The best part is it is broken down into 118 "tips" that are the heart of the book. I won't give too much of the book away, but the first tip sums up what is typically the crux of the problem:
Distinguish between estimates, targets, and commitments.
And Steve gives a suggested reading path for people who "need to create an estimate right now" (i.e., me and my team).
I like this book because it is focused on one thing (software estimating) - one absolutely critical thing.
We need more books like this. We can't just have the Mythical Man Month to turn to.