Building new software requires an estimate
for the project owner how long it will take (and how much it will cost).
This is one of the dark arts in System Architecture. Unless you repeat
a previous exercise 100% you are limited to guesstimates. And you NEVER
repeat a previous project 100%, since there would be no need, just use
last times results.And
guesstimates are a waste
On my Sunday blog tour (while Anthony
and Ernest mess up the house <g>) I came across
a very true quote:
"We spent so much time arguing
whether or not it work, and when we prototyped it, it worked remarkably
well. We could have saved so much time, if we had just build it sooner."
Another reason to do paper
This site is in no way affiliated, endorsed, sanctioned, supported, nor enlightened by Lotus Software nor IBM Corporation. I may be an employee, but the opinions, theories, facts, etc. presented here are my own and are in now way given in any official capacity. In short, these are my words and this is my site, not IBM's - and don't even begin to think otherwise. (Disclaimer shamelessly plugged from Rocky Oliver)
© 2003 - 2013 Stephan H. Wissel - some rights reserved as listed here:
Unless otherwise labeled by its originating author, the content found on this site is made available under the terms of an Attribution/NonCommercial/ShareAlike Creative Commons License, with the exception that no rights are granted -- since they are not mine to grant -- in any logo, graphic design, trademarks or trade names of any type. Code samples and code downloads on this site are, unless otherwise labeled, made available under an Apache 2.0 license. Other license models are available on written request and written confirmation.