Game Development Stack Exchange is a question and answer site for professional and independent game developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What is the best (as in most used by professional game developers and/or companies) software development methodology used in game development?

I've heard that SCRUM is popular, but i'm not sure.

share|improve this question

closed as too broad by Josh Petrie Sep 4 '15 at 4:16

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.

up vote 14 down vote accepted

Honestly, it depends on the size and history of the team.

Most of the large teams I've worked on have utilized an adapted version of Scrum. Often, a studio will bring in Scrum instructors or require producers to get "Scrum Master" certification.

As noted above, Spiral is an option.

Generally, some sort of Agile development is used that involves stand-ups, product owners, etc.

There really isn't a "best methodology." Team size and experience dictate the correct process to use. If you're a believer in Lean, you'll also understand that process is very specific to the tasks at hand.

share|improve this answer

The Spiral model is very popular for game development. Due to the fast changing development cycle and the size of most game projects.

Since game development is a living project and most game projects are not defined well before the project starts. The spiral model allows for fast changes and flexible development.

share|improve this answer

While Scrum is fairly popular, in my experience it only works if both the team and the management are willing to stick to the plan.

share|improve this answer

Cowboy seems to be popular...

share|improve this answer

Whatever methodology you choose, you need to keep in mind that a game at all stages, needs to be fun. The methodology you use will really come down to the team members involved and how many of them are, but at all points you should be able to "play" the game in some form to evaluate if something is working or not. That great design idea that takes weeks of development and does not add to the fun factor is wasted time. Having an Agile methodology should enable you to evaluate each feature of the game as it is developed.

share|improve this answer

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