In order to obtain a perspective from each team member we will be making all decisions within a group consensus.
How will you communicate? Email, meetings in the lab, discussion board?
We have decided to meet every Monday and Friday on top of our regular lab hours. We will use e-mail as a communication medium extensively when we are not meeting together. We will also post essential information on the web forum so that we can have static resources for each team member to consult.
How will you know when you're off schedule, and how will you deal with schedule slips?
Based on weekly meetings and discussions we will be able to analyze all progress. From this analysis, we will be able to determine if our progress is acceptable in such a manner that will allow a successful project completion. If necessary, team members working on other components will help wherever development is falling behind.
Who will produce the weekly group status reports?
Each individual is responsible for providing status for his weekly schedule report. As a whole, we will sit down during the meetings and update the group status report on the website as a whole.
Each component will be unit tested individually before integration. After integration we will test the project as a whole.
How will you do documentation (both internal group documentation as well as external player documentation)?
We decided to design the interface for each component as a group so that we would be able to implement each component individually. Each component will be responsible for documenting all component implementations as well as their ongoing changes so that other component developers will be aware of all changes.
External documentation will be handled as a group so that we can determine what a user would need to know in order to play the game and understand the storyline.