It depends. If the project built up of slightly different modules, putting
the coders on a big, white table seems to be a good idea. But if the modules
are completely different, you should separate them, so each of them can be
focused on their own subject. In this case, you have to have some people to
make the whole project as one, seeing other programmers' works to combine.
There are many tool you can use to manage the project. (I personally like
open tools, like OpenProj which compatible with Microsoft Project, and if
you want to have version controlling, I can suggest Microsoft Visual
SourceSafe, or JEDI VCS). Each of them can handle a variety of subjects.
OpenProj can organize jobs, and resources. Microsoft VSS and JEDI VCS are
version controlling systems, which can handle the code itself, you can
check-out modules, make changes, then check-in, so others can use your
module as well. (and if you screwed something, you can change back to a
previous version).
I hope you can use these advices. And I think, your question is not
definitely PHP question ... :)
SanTa
----- Original Message -----
From: "Ronald Wiplinger" <tm.ronald@xxxxxxxxx>
To: "php-general" <php-general@xxxxxxxxxxxxx>
Sent: Tuesday, January 22, 2008 8:40 AM
Subject: Tool for programmer team
What is a good tool to coordinate a team of programmers efficiently?
To give each one a different part of the project is a start, but it needs
to
get combined at some points to be a working project.
Not to debug code you have written was a hint, to see actually bugs as a
bug
and not as a feature.
Some hinted let programmer be on different places, others say put them
together on a big table, ...
Where can I find more information about that subject?
bye
R
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
