Thanks for comming down and doing that talk, it was ther first one I'd ever heard about project estimation. Made me really think about how to handle those types of things in the future

I liked the topic since it's something that is rarely talked about but obviously has a big impact on the perceived success of the project. I would talk more about what all you take into account when you estimate a task and what things you include when estimating a task (e.g. coding, writing tests, fixing bugs, etc.). Maybe have an example feature and take us through your thought process as you're trying to think of everything that will affect your estimate.

This was a very nice talk, with lots of useful info. I agree with Kruger though, that a breakdown of the different steps would be good, including the fact that a project isn't "done" if stuff like unit tests and basic documentation you need if you're ever called back to work on the project are done.

One other thing that would be cool: Consider making the powerpoints available for download online. There are a few slides i wouldn't mind showing my boss :)

But again, overall a very fun and informative talk. Keep up the good work.

I really enjoyed hearing a talk that took a step back from all of the technical talks we typically hear. Good to be reminded of all the other influences going into developers (and other project team roles) delivering an end product.

One thing I find interesting is listening to speakers such as yourself who are consultants (as am I) delivering to non-consultants. Seems like the crowd had a number of questions relating to how you operate in regards to the topic when their personal dealings with the subject matter will probably be drastically different. On the other hand exposure to how things are on the "other side of the fence" does open up some room for discussion and hopefully enlightenment.

Only thing I would add is that in the beginning you said you'd like the talk to be a little bit of discussion. If that is a goal have some points where you get direct feedback (maybe even a plant like Blankenburg or Bender to start the ball rolling). Thanks for taking the time to speak. I'm starting out speaking at events and I know how much time and pressure goes into it.

I really like the topic especially since I will be going to estimate my first freelance programming project this week. One thing I found very helpful was his talking about breaking the longer aspects of the project into smaller pieces. It sounded to me like he was suggesting we architect the code during the estimating process so that we make more accurate estimates. I found it very useful and he provided some reference materials that I can pickup to work on becoming better at my estimating. Thanks!