In our team we are using agile methods by making sure that we always have a product that builds and plays properly and it is always being incrementally being built. One of the things we started out with was that we properly built a character and a small level 1st that is playable and every week with the evaluator we would show how the product evolves and what kinds of iterations we will be building for the next week.
In other aspects of agile methodology we are going through the phases of talking to each other and making new changes on the spot. So for example when we found out that scripts for disappearing walls can work on other objects and character, we started to apply to different things in the game to make it more interesting.
Some of the risks we associated with agile methods is that it is very hard to kind of estimate the time when the the project will be done. Sometimes we are done early and we don't know if we should expand it to more quality or complete the functionality in the next iteration of our build.
The trade offs of using agile is that we can adapt easily to changes and at the same time always see how our game progresses. With other methodologies like waterfall we would not have a working build till the end as everybody would be working on different stuff and just integrating a finished product at the end. Thinking about using waterfall method for this type of project would actually be difficult to see...
No comments:
Post a Comment