How do you document your web development?

Plain Email
29% (4 votes)
Live Online Chats
14% (2 votes)
Phone Conversations
21% (3 votes)
Wikis
7% (1 vote)
Discussion Forums
7% (1 vote)
Blogs
0% (0 votes)
Other (Please specify)
21% (3 votes)
Total votes: 14
JeevesBond's picture

He has: 3,956 posts

Joined: Jun 2002

It's interesting to see everyone's methods. I use Basecamp to control timelines etc. Like the idea of having a Wiki for spec writing, that's a good one. Maybe you could just get an e-mail to show client agreement? That should be enough.

Am wanting to switch to Trac: it's Open Source (so free in both senses of the word), is built for software development, has a wiki. The only problem is that it's a bit hard to install and has lots of dependencies (Python, SVN etc.)

a Padded Cell our articles site!

He has: 1,758 posts

Joined: Jul 2002

I take the specification from the customer by email/phone/meeting etc then write it up in a simple to understand format. Once it's done and the customer is happy with it I send it to the customer and they have to print, sign and return it to me by fax or post. Once that's done the spec is locked and can't be changed (unless of course they are willing to pay more money for me to revisit the spec and the extra development work).

I used to be really flexible, but I got taken advantage of too many times so I implemented this really rigid method.

Andy

pr0gr4mm3r's picture

He has: 1,502 posts

Joined: Sep 2006

Ah, yes. Forgot face-to-face meetings. I've only had a few of those because most client find me over the Internet.

timjpriebe's picture

He has: 2,667 posts

Joined: Dec 2004

Don't forget face-to-face meetings. Smiling That's my standard way.

And personally, I try to make sure the specs are all part of the contract and are pretty clearly spelled out.

Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.