3

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?

DarkwingDuck
  • 2,686
  • 24
  • 29

3 Answers3

2

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:

Rinat Abdullin
  • 23,036
  • 8
  • 57
  • 80
0

Concerning code quality checking, architecture exploration, code versions diff and more... you can have a look at NDepend.

Patrick from NDepend team
  • 13,237
  • 6
  • 61
  • 92
0

look here for Application Life Cycle start point

ALM + TFS Links here

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

(Windows app, Server)

Ric Tokyo
  • 6,577
  • 3
  • 30
  • 48
  • I'm after recommendations really: what do other people actually use? The wikipedia link is good for a list of tools, the other link is purely TFS related and I am already familiar with that. I was after user stories with tooling support. Thanks for answering though (no one else has) – DarkwingDuck Jan 27 '09 at 05:51
  • Yes, basically I use Git and Project Server for ALM that and default SharePoint functionality. to be honest, the question should be: What tools do you use for Application LifeCycle Management? – Ric Tokyo Jan 27 '09 at 06:04
  • TFS is a tool and I asked for alternatives. I'd say that implies tools in the alternatives. :) – DarkwingDuck Jan 30 '09 at 00:47
  • Yes, I think Application Life Cycle Management via Git and Microsoft Office Project implies an alternative methodology in itself. – Ric Tokyo Jan 30 '09 at 02:28
  • Ok because you mentioned that you use MOSS for project management, and PM is different to ALM. I'm more interested in things like support for release management, configuration management, etc. Can you explain how MOSS helps in these scenarios? Because its certainly not built for those purposes. – DarkwingDuck Jan 30 '09 at 23:20
  • that link about tfs + alm is for a post written in 2007 mentioning vs 2005 – Juan Zamudio May 23 '11 at 20:33