Minimum project management tool set

1. version management tools and text comparison/merge tools
YesCVS: turtles and winmerge.
In the past few years, do anyone dare to work with people without using version management tools? Yes.
A good programmer, in addition to good udpate/commit habits, will a good use of text difference comparison/merge tools be another level of observation criteria.
In addition, because refactoring is useful, version management tools must be integrated with IDE.

2. Project Plan, task allocation, demand change management, Bug management tools
By accident,I found myself handing over all these items to Jira.

Project planning, task allocation, progress tracking, demand change management, and Bug management are almost all tasks of PM.
In the past, there were always a lot of software to manage these problems separately. Copy several paste software for the same problem.
However, if your team's project plan is in the XP plan style rather than the MS Project
Congratulations,IJIRA to complete all tasks.

3. Support refactoring, flying error prompt, TDD and debug ide

Java:Idea 5.0 can meet all the following requirements:.
C ++:Vc7.1 +VA, It is much worse.
RUBY: EclipseRDTPlug-ins are weak.
GROOVY: idea plug-inPolicyj
PHP:Zend stuido

Sometimes, I also use eclipse + commercial, free plug-ins instead of opening so many ides above.

A. refactoring: even if the team only uses rename, move, extract method, and other basic functions, there are too many things in the J2EE structure, refactoring will help you clean things, and now the dependency has been formed.

B. Flying error prompt:
Standard configuration of Java ide. Prompt immediately when there are errors. Do not wait for compilation. Unfortunately, this is not a standard in IDE in other languages.

C. debug J2EE applications:
Web developers generally use system. out or log4j to display debugging information.ProgramPersonnel, directly go to the debugging mode, track the program execution path in a single step, and check which variable is needed. This is just a matter of course, but it was not supported by the IDE.

D. TDD: TDD is not equal to unit test. TDD eliminates the need for dependency on the presentation layer, manual data input, data clearing, and tomcat development.
Our team cannot afford to test coverage for the moment. So and unttest are just a development method, not a testing method.

4. Team im tools and Shared Folders
The previous generation is a must-have email.Google GroupIt is also very useful, but we prefer the Real-Time QQ group.
At the same time, the "show only the number of messages when messages are sent" feature of QQ 2005 is very important.
For teams sitting together, creating a shared folder on the file server is enough.

5. Knowledge Base Wiki
JavaJspwikiIs the most simple and easy-to-install entry-level wiki, cofluence 2.0 finally has a WYSIWYG editor.
There are other options in the PHP world, suchDokuwikiAnd Wikipedia.

Other tools include paper, pen, a large enough whiteboard, and meeting rooms available at any time.

What else is missing?
I,CodeThe automatic generation tool is not the best tool.
2. because there are not enough unittest cases, the continuous integration tool is not actually used.