Methodology Article

Awhile back I came across an article on gamasutra about game design software methodologies; I thought it was a useful read.

The article gives a brief introduction to Scrum as a game design methodology. While I don't think Scrum as a whole is what we need (daily meetings are overkill, for example), some of its elements would be great for our project. Things like emphasis on the entire team working together, "vertical slices" as intermediate deliverables, frequent customer meetings for feedback, short work cycles, and the fact that it's an iterative process could be easily worked into a methodology.

I'm not entirely sure we're supposed to have a formalized methodology (although I seem to remember hearing that we're supposed to stick to a methodology at some point), and I'm not sure whose job it would be to run it (probably Amanda's, but again I don't know). Just throwing this one out there in case.