Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

A small group of friends (including myself) decided to develop a simple 2D game. We are all fairly new to software development, so I wanted to ask which software development model would likely work best for such a group. From the list on Wikipedia, the Waterfall and Spiral models seem to be the two best options.

Our plan is to use C# with XNA for development.

share|improve this question

closed as not a real question by Glenn Nelson, gnat, ChrisF Jan 31 '13 at 9:04

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
If it's small and impersonal go Agile. You won't need all the ceremonies but will probably end up working Agile-ish after a while no matter what you choose –  James Jan 31 '13 at 4:06
    
This is a list answer question and as such is generally considered unacceptable for our Q&A format. –  Nathan C. Tresch Jan 31 '13 at 5:42
add comment

1 Answer

up vote 2 down vote accepted

If you're new to software development, then the different software development models probably won't make much sense. Although I had studied (in school) and later read books about software development methodologies in the past, it probably took me about two decades (and ending up in a suitable industry) to truly understand what the so-called "Waterfall" process really meant and what information gets transferred between each step.

As a novice programmer, you are going to have to dedicate so much effort to actually developing software, that most of the "process" that you read about will seem like frivolous annoying bookkeeping. Believe me, you're not going to want to worry about cross-referencing the sections in the Software Design Document with the requirement numbers in the Software Requirements Document, when you've just got jumping working but there's a bug when you try to fire at the same time.

share|improve this answer
    
Definitely true. One particular thing I do need to figure out, however, is how much planning & design to go through before we begin the coding process. Would it be better to try to make a fairly complete map of the objects & methods & such, or just go over a vision of what we want and the basic necessities of how to start working towards it? –  aaronncfca Jan 31 '13 at 4:50
    
I would start with the simplest thing that can possibly work. Get a framework doing something useful, and then build on that. If you spend a lot of time designing your object model and methods and whatnot before getting anything actually happening, you're going to lose motivation and momentum fast. –  Greg Hewgill Jan 31 '13 at 4:56
add comment

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