Question

Recently I was tasked with writing up formal procedures for a team based development enviroment. We have several projects with multiple modules each. Right now there are only two programmers, however there are plans to expand to 4-6 programmers. Each programmer will be working on the same project and possibly pages which may cause over writing or error issues.

So far the ideal solution I have thought up is:

1. Local development (WAMP/VM or some virtual server instance on their own machine). Once a developer has finished their developments, they check it into the CVS Repository and merge it wih other fixes etc.
2. The CVS version is then deployed to the primary dev server for testing by the devs.
3. The MySQL DAtabases are kept on the primary dev server and users may remotely connect to it. Any Schema / Data alterations are run through a DB Admin who will notify all devs of any DB Changes (Which should be rare).

Does anyone see an issue with this or have a better solution?

Answer 1

Looks good. Just wanted to highlight this one very important point:

Make sure you have nightly builds in to the dev server. This will help catch problems at very early stages

By the way, while we are at it and in case you arent aware, Joel has a very good 12 point system for Quality of a Software Team

Excerpt

1 Do you use source control?
2 Can you make a build in one step?
3 Do you make daily builds?
4 Do you have a bug database?
5 Do you fix bugs before writing new code?
6 Do you have an up-to-date schedule?
7 Do you have a spec?
8 Do programmers have quiet working conditions?
9 Do you use the best tools money can buy?
10 Do you have testers?
11 Do new candidates write code during their interview?
12 Do you do hallway usability testing?