1. get outline of expectations
2. write simple summary of functionality - confirm with sponsor
3. write tech specs - method, db table, flow etc summary - pass round dev team to see if you missed anything
4. write, pass on for code review (informal)
5. check in with sponsor for any feature additions
6. pass to QA, listing params expected on each iteration (web stuff :) so can be hammered
7. publish to Beta server
8. write end user docs, support docs, dev docs
9. publish to live servers

Well, that's the theory, anyway :)

tilly just leant me Peopleware, and I've found that very useful, and Rapid Development, that I have yet to make a large dent in. I think both are worth reading though.

And no matter what environment you're in, argue for clear docs from the start, and testing. It *will* save you time in the long run.

I guess it all depends on the environment you work in though ;-)

.02

cLive ;-)