Agile Estimation?
If you can't write a design until you write some code, how do agilists (or agilistas - you decide where you sit) - do estimation?
I am really curious. I have, and do, do the COCOMO thing, function points, and other techniques. Occasionally, if I think the app is CRUD enough, I go down to "screens" based estimation... but more or less, I am interested in the details that drive you to think "40 hours" versus "8 hours". And if you are doing agile and TDD, how you can ever come up with an estimate at all, at least before you write some tests which allow you to know... perhaps... what classes, and even more perhaps, what the FP of those classes will be, in your estimate.
I ask this not because I think estimation of effort up front is a good idea. Largely, I think, it is a guess that we do given the information we have at the time, which, more often than not, is usually insufficient. But every agilista is making a living, and if you are doing so, the people that, I dunno, pay you, are asking how long you think something will take, even before you have written the HOLY tests.
Just curious... cause I am stumped.