The level that the project manager, System Architect, or technical backbone should possess (3)

[Transferred from www.scmlife.com]

Iii. Development Stage

1. Configuration Management Tools

 

There are many code management tools. Currently, the company uses many code management tools including CVs, VSS, and SVN.
There are only 2-5 developers in a development team and the two are in the same office. Using VSS is a very good choice. I personally think that the management of his small team is very useful. I personally think the only drawback of VSS is that when a file is locked by one person, no one else can modify it. When a file is shared by multiple people and there are a large number of developers, this problem will be very serious. You can find both the VSS client and server in Visio Studio.

VSS client plug-in for Eclipse: http://vssplugin.sourceforge.net/

If you have more than five developers, selecting CVs or SVN is a better choice. If your team is scattered, it may not be in one office or in the same city at all. Using CVs or SVN is a much-preferred choice. CVS servers generally use cvsnt or cvsserver.

Cvsserver:
Linux for x86: http://ftp.gnu.org/non-gnu/cvs/binary/stable/x86-linux/RPMS/i386/
Windows for x86: http://ftp.gnu.org/non-gnu/cvs/binary/stable/x86-woe/
Cvsnt: http://www.cvsnt.org/
Cvsclient:
Wincvs: http://www.wincvs.org
Tortoisecv: http://www.tortoisecvs.org/
Integrated CVS clients for JBuilder, Eclipse, netbeans, and idea

As a version management tool, CVS has been around for 20 years. It can be said that it has come to an end, but it is certain that it will continue to exist. SVN emerged as a replacement product of CVS. Now many open-source organizations are slowly switching to SVN, such as Apache and SourceForge. SVN has more powerful functions than cvs. For example, it can record directory changes and its performance is much faster than CVs. Currently, SVN is gradually accepted by enterprises, but I personally think that the stability of its eclipse client is still to be improved. This may be related to the version compatibility of Eclipse. However, these instability make my use of this product continue to be in the trial phase.

Svnserver: http://subversion.tigris.org/
Svnclient:
Tortoisesvn: http://tortoisesvn.net/
Eclipse Plugin: http://subclipse.tigris.org/
Currently, SVN plug-ins support development tools such as Eclipse, jdeveloper, and netbeans.

 

2. Knowledge Base Management Tools

Each person in the team will find some problems during development. In the end, some problems may not be solved, and some problems can be solved. Generally, most problems can be solved through the joint efforts of team members. knowledge should be formed in the solution and steps to solve the problems. As a leader of a team, we must pay attention to this knowledge, because it is very useful and can provide corresponding help to some new users or colleagues who have not encountered such problems.

Confluence (http://www.atlassian.com/software/confluence), a product from the same company as Jira, can be well integrated with Jira. We can use the issue of Jira to turn this issue into a knowledge. If you use Jira for project management and defect management, using Confluence is the best choice.

PhpBB (http://www.phpbb.com), the Forum is actually a very good knowledge base management tool, when an engineer encountered some problems, eventually, through their own efforts or the efforts of other colleagues in the team, finally solved the problem. As a leader, you should encourage them to write some articles about this knowledge and publish them on the company's own bbs. For your reference and discussion. This is a good method. I remember when I saw some useful information on the Internet, I saved it on my native phpBB. Poor, but the computer was stolen. Thieves are depressed.