Infrastructure for a software project [closed]

Question

I'd be leading a new project soon. And I've been pondering over what are the basic infrastructure for a software project. These are the stuff that I think every project should have:

-Coding style conventions

-Naming conventions

-Standard project directory structure(eg maven standard dir layout, etc)

-Project management and issue tracking(eg trac, redmine, etc)

-Continuous Integration server(eg, hudson, cruise control, etc)

I'm not sure if I missed out anything. Would anyone like to add?

Answer 1

As a preliminary answer, check out the Joel test: http://www.joelonsoftware.com/articles/fog0000000043.html

Just an appetizer:

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?

Answer 2

• revision control system (eg. subversion, cvs, git)