Friday, March 2, 2012

Late Homework 3 Entry: How our team is using Agile methods this term

Although our team does have an overall schedule to abide too, the overall development process thus far has actually been very Agile like in its methodology. For example, even after creating new pieces of code or assets, we often seemed to have found ourselves, going back to the code or art, and refactoring it for efficiency, or in the case of art, perhaps even willing to create newer better models for use in game.

We also have broken down our schedule into small manageable steps, where we allot different amounts of days to different tasks based on perceived difficulty in order to finish them in a more timely manner. However, much like Agile developmental methods, if the task requires more time than usual, we may put it off to work on another task and return to it later. In our case for the Alpha build, we actually managed to finish some tasks early such as the lighting mechanic that changes the game environment's wall layout, giving us precious time to work on other new features.

In essence, since we are using a very flexible developmental schedule, with smaller tasks to complete in set amounts of time, our team is using Agile processes. The additional use of frequent weekly meetings, email correspondence, occasional pair programming, client (TA) meetings and other Agile techniques has thus far been very useful in our game's development.

No comments:

Post a Comment