Take the 2-minute tour ×
Game Development Stack Exchange is a question and answer site for professional and independent game developers. It's 100% free, no registration required.

Other than using a wiki, what good (or purpose-built) tools allow for collaborative work on a game treatment?

I have a couple ideas I'd like to get fleshed-out and built, and have a small team who will work me on the project(s). How can we best iterate-over and define the game-play, graphical styles, etc?

share|improve this question

closed as too broad by Josh Petrie Oct 24 at 17:41

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

2 Answers 2

up vote 6 down vote accepted

Personally I think your best bet is to use a funnel-like process.

  1. Team generates ideas. No criticism at this point just write stuff down. Wikis, Skype, group chat are all good tools here. Each person should generate ~20 ideas at this stage.

  2. Filter through ideas. You can do this alone or with the team. Most likely start by picking a few key qualities to optimize for. (e.g. novelty, depth, time to create.) Put ideas into buckets, start eliminating ones that don't meet the cut. You should end up with ~1 idea per a person at this stage. Consider using Excel or Google Spreadsheet to help you slice & dice and visualize your data.

  3. Prototype ideas, still no coding or very limited coding. Best bet would be to use pen & paper to draw out some of the interactions. You could also use something like XNA, Game Maker, or Flash to prototype ideas quickly and cheaply. Identify the best one at this point.

  4. Implement more features in waves, no more than 1 day per a feature. At the end of each day test what you have and measure it against the qualities you were optimizing for in step 2. Cut the features that don't seem to be helping and do more of the stuff which is. Most likely use version control to distribute source code for prototypes, e-mail, a wiki, etc for feedback.

Tools to use:

  • Git, SVN for version control
  • DropBox, Git, SVN for distributing builds
  • E-mail, Wiki, Google Docs, Google Wave, Chatterous, Skype for feedback, discussion
  • GitHub, Mantis, Jira for issue tracking
  • SCRUM, Kanban for development process
  • Excel, Google Spreadsheets to work with feedback / break features down and visualize results

Edited to add mention to spreadsheets, we often forget it but Excel is easy to use, powerful, and creates visuals which communicate a lot quickly

share|improve this answer
1  
+1 Great answer, everything I was going to say plus more –  SD021 Jul 26 '10 at 21:18
    
that's exactly what I was trying to figure out! Thanks! –  warren Jul 27 '10 at 17:52

Git + Sphinx is the best solution I've found lately. Substitute git for hg if you prefer, but the general principle is the same. Wikis are generally not so good for such a highly structured document will multiple concurrent editors.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.