Probably because I work in the private sector, estimating the time, time-line (and rate per hour) for a project is a necessary evil. That said, it’s a difficult balance – well more like trying to balance (if not spin) a plate on your finger. Because you are usually bidding for a contract, you need to be conservative with you time but promise the moon (not the sun & certainly not the stars: never over-promise!) while being realistic as to what you can actually deliver and still be profitable. Often this is done with very little concrete knowledge or information about the resources available, stakeholders or expected outcomes. I’ve consulted on more than a few educational projects (with an animation company) – some for the public sector and some for the private sector – where I have had to define the project for or educate the client after the contract is signed as to what is and is not possible given the agreed upon timeframe and budget, particularly with regards to the development of ‘bells and whistles’. As much as developing an online course (well, any course, for that matter) should be about the learner’s needs – particularly with respect to content and objectives – more often then not, and while it may begin with the learner, it eventually comes down to a question of time and money.
That aside, and I think especially when working with technology, having a timeline is a good thing for any course developer as it helps keeps you focused and efficient for IT is rife with distractions – from allowing you to be niggly about aesthetics to providing far too many paths to finding that ‘perfect’ piece (article, video, audio) to just plain enticing you to go off on a tangent all your own.