Okay... I am flabbergasted. After developing software for about 10 years now, I have to tell indiestone: USE A BUGTRACKER. Having a bugtracker will help you in the long run to avoid unnecessary work although it may feel like you get too much administration work. This administration work - which you undoubtely have to do at the beginning - will easily pay off once the thing is running. Furthermore you can integrate most bugtracker into your versioning system (like github or svn) enabling you to keep track of features and milestones/versions. If you are interested in this topic, I can search for a few links which elaborate more clearly. Edit 1: ... and lots of administrative work once the bugtracker is running can be done by your nice forum admins. Edit 2: You can also use a bugtracker for internal communication. Which means you can write bugs/tasks for other team members when you need work done. This have several advantages over e-mails: You can keep track how much of the work is already done by looking the task in the tracker, you don't need to remind people of that mail which you sent two weeks ago, since the bug will be assigned to them and won't get lost (at least not until it is "closed"), when someone needs further information they can comment on the bug and assign it to whomever has the information who can then answer and re-assign the bug. It's definitely easier than communicating by email and they won't be any information loss like when you use mails.