I'm also familiar with the 'Subversion + Cruise Control + Fogbugz + nCover + ...' setup used in dev houses. But what other options are there? I'm pretty naive outside of these 2 combinations. I'm from the .net world and perhaps LISP of Ruby developers do it completely differently?
Hi, look here for Application Life Cycle start point
What some people do (me for instance) is to simply have Git doing the source version control and perform project management separately with SharePoint (WSS 3.0) or MOSS and/or with Microsoft Office Project
I'm mostly into open-source software stack for developing in .NET (except for the Microsoft Project which does not have any alternatives when you need to handle really complex projects).
In short, primary software ingredients are:
- CruiseControl.NET
- Subversion
- Trac (issues + wiki + SVN) / Google Code for open-source projects
- NCover, NUnit, FxCop, SandCastle, Wix, Lokad Shared Libraries, Autofac, FxCop etc.
Project management approach: start projects in a PM style (a lot of planning, clarification and prototyping), get to the first release (minimal functionality, all services are mocked, plain UI), then turn on continuous integration and switch to Agile (while still using PM to plan and schedule on a larger scale).
Related links:
Concerning code quality checking, architecture exploration, code versions diff and more... you can have a look at NDepend.