The team consists of Adam Stack, Horica Ionescu, Remo Gutierrez, Michael Paulsen, Tyler Harbin-Giuntoli, and Ross Pape. Adam is the document manger, making sure documents are ready and turned in by deadlines. He will coordinate with the team to ensure documentation needs are met. He has the final say on documentation standards, style and content. Horica is the documentation and testing assistant, will assist the document manager and testing lead, as well as managing communications and meetings. He will have final say on meeting times. Michael is the testing lead, and he will organize and run bug testing as well as automated testing. He has final say on enforcing necessary changes to code. Remo is the lead developer, and he will organize program structure and keep objects within a coherent vision. He is responsible for keeping object input/output consistent. He has final say on accepting or rejecting proposed objects, features, themes, and styles within the game. Ross is the developer assistant, and he assists lead developer and streamlines code by refactoring. He is responsible for keeping object input/output consistent. He has final say on code style and naming conventions, as well as inputs/outputs of objects. Tyler is the developer assistant and general manager. He assists lead developer and is in charge of general group organization. He has final say in mediating disagreements. Communication is handled through Facebook and text messaging. Certain meetings will be held in person, though the majority of the time communication will be maintained online.

The process our group will follow will resemble the V model for the most part. The important aspect of this model is that through the testing process, the design will be revisited to ensure that all system design aspects are implemented correctly.

There is no set Operating System that will be used, as each team member will use their own preferred OS. C# will be the programming language we use, as it is the language compatible with Unity.

Version control and change control will be the responsibility of Remo the lead developer. He will collaborate with Ross, the developer assistant. If they need assistance, other team members may be asked to contribute to the process.

QA activities will be the responsibility of Michael the testing lead. Horica the documentation and testing assistant will assist in the process. Each of these activities will occur when major sections of the game is complete. The results will be reported in documentation.

At a minimum, each team member will post the following information weekly: individual time and activity log, individual status information, individual issues and problems, and individual defect log.

Each week, the project manager will: read and analyze the logs; examine the technical content of the work done to date; examine the technical progress metrics; consider the QA results; reassess the potential project risks; and take corrective action if necessary.

The project manager will issue a Project Management Report on the schedule as indicated in the deliverables section above. At a minimum, the Project Management Report will be generated every two weeks and will include the following information: 1 sentence description of overall status, 1 or 2 sentence of any planned changes to the project plan, graph of planned vs actual time, graph of planned vs actual for each technical progress metric, updated PERT chart."