Final Project

Teams

Team #1: Siphon (Resource-Based Multiplayer Space Battle)

Alex Weitzner: Team Lead, Programmer, UI, Version Control, Playtests
Alex Hartman: Programmer, Creative Lead
Katie Rosell: Art Lead, Concept Design, Scrum Master
Luke Seaboch: Art, Audio

Team #2: Wigglemeister (Funny, Mechanics-Based Movement Challenges)

Clay Stewart: Art, Scrum Master
Andrew Fulop: Lead Programmer
Jarrod Osofs: Programmer
Chad Reilly: Art

Team #3: Historic Fractures (Asymmetrical Historical Character Battle)

Jimmy Madio: Lead Artist, Scrum Master
Alex Clark: Animation, Sound, Art
Sean Murphy: Level Design, Programming
Nicholas Molina: Lead Programmer

Guidelines

Team Makeup
  • Students may pick their own teammates. Teams of three to five students will be allowed to work together without questions asked. (note: to facilitate this, teams must be willing to include additional teammates if asked.
  • Each team should have the following roles identified. Leadership roles must also have additional production roles as well (e.g. UI design, sound design) (note: a team member may take on multiple leadership roles, but will be responsible for all responsibilities listed):
    • Team Lead: Responsible for general leadership of the game's production. Ensure the functioning and well-being of the team. Resolve disputes. If there are team issues, this will be my point of contact.
    • Scrum Lead: Responsible for organizing task lists w/individual team members. Ensure effective communication w/r/t development. Ensure integration.
    • (Consider): Art Lead, Programming Lead, Design Lead.
  • Students are highly encouraged to write up a simple agreement before starting on the project. Consider the potential life of the game outside of the classroom.
Mission Statement
  • All teams should be guided by a clear mission statement. It's OK for that mission statement to change, but you must announce to the class when it's changing.
  • The mission statement will be use both to guide your development and decisions you make as well as how your game will be evaluated.
Design Document
  • Teams will work together on creating one game design document. The document should consist of both written and visual documentation. Students will be graded on their individual contributions to this document, so mark your contributions clearly.
Process
  • Students will be required to implement a simplified version of SCRUM, which will entail weekly sprints. Teams may use Trello, Google Documents, or Office365 to organize their process. Other software can be approved upon request.
  • Students will be evaluated on their individual progress which should dovetail with the weekly SCRUM documentation. These grades will consider both the quality and quantity of individual efforts. Students must document their individual contributions on Trello through a weekly completed task list (e.g., artist should share artwork and screenshots, programmers should share tasklists, builds, code, and screenshots).
  • After the first week, there will be a quick deadline for a successful MVP. All teammates must work towards a successful completion of this task. Artists should consider creating paper prototypes when appropriate.
  • Class time will be one of the following formats:
    • Presentations: Every week, teams will present progress. We may consider having one team or overflow presentations the next weekly meeting depending on number of teams.
    • Playtesting/Evaluations: Every other week, we will have a playtest eval session. Each student must play all class games (aside from their own). Playtests questions will have a few general questions, with the option to add specific ones as well. These evals will be graded in some way (either as a cumulative eval grade or maybe a part of biweekly individual grades).
    • Development: Every other week, we will have development days. I will check in with each team during this time.
Project Grades

Specifics forthcoming. Roughly 30-40% will be shared grades, roughly 60-70% will be individual contributions.

  • 12% — Game Design Document Grade (individual)
  • 12% — Week 1-2 Grade (individual)
  • 12% — Week 3-4 Grade (individual)
  • 12% — Week 5-6 Grade (individual)
  • 12% — Week 7-8 Grade (individual)
  • 6% — Playtest Grade (individual)
  • 12% — Midterm Grade (shared)
  • 22% — Final Grade (shared)