On the previous entry a poster asked:
Although scrum sounds good for prototyping, and it sounds good once you have a potentially-shippable game that you're polishing, it doesn't seem terribly useful for that phase we call "full production", where (ideally) we're creating a big pile of content using systems that have already been developed. Or am I missing the point?
This is a great point and one that we are trying to address for our next project. I believe that "incremental" development is less useful when you know your requirements and your technology. Take a look at slide # 5 in the presentation. When you are in the situation that you describe above, you are in the "simple" zone of product development. In this case, your process can be more waterfall. You can preplan up front and depend on that plan.
However, this isn't to say that Scrum is not useful in this stage. For example, meeting every day for 15 minutes to discuss progress and impediments is just as useful. Doing a burndown of progress is just as useful. Same goes for having visible progress in the game.
As Ken Schwaber likes to say: "It's about common sense". Scrum encompasses a number of good practices that are as minimal and non-intrusive as possible. If something doesn't make sense to do, then don't do it!