Project methodology for small teams [closed]

Question

We're usually 1-4 developers / art directors / copywriters on each project at my firm, what methodology would you recommend use to use? Agile? XP? Scrum? Something else? (I know they are all variations of essentially the same concept, yes)

Answer 1

I don't think there's a general answer for it, the question is too broad, and you can't just "adopt a methodology" as if it were a product that you take out of the box, it's something that you evolve over time...but in any case I highly recommend you getting a copy of this book: Head First Software Development

Then you adapt the ideas you like into your project. Don't worry about names and buzzwords, they will be all "passé" next year anyway. Keep it simple at first, adopt the ideas that make more sense and give the most bang for buck, and don't try to solve problems that don't exist yet. It will be a very good start.

Answer 2

For pair programming, at least, it's best to have an even number of programmers... ;P

One of the good things about small teams is that you don't need a lot of support systems to communicate internally (a bugtracker becomes more or less a todo list for yourself, but it's good to have anyway). If having a meeting with the whole team just involves turning around your charir and say "Hey, Bob and Carl, take a look at this!", you don't really need all formal rules of a methology anyway. But agile methods in general is quite well suited to small and medium sized teams, but they require self-motivated team members.

I'll say pick whatever ideas you like from the different methologies, they can be considered suggestions anyway.