Groups usually pick one aspect of the project to update or add. They usually form a team to complete their proposal. Often teams are made up of artists and programmers just like in real software or web production groups. Here is some info on past teams, so you can get an idea of how proposals and teams are created and work.

 

At Stanford, the large class broke down into many groups. See the credits page for how they broke down, notice the team names and how they had programmers and artists on them. Some times all programmers and all artists, but mostly they had both - the project dictates what is needed for a team to do.

facade stanford credit page

SFU teams

2003's class had 5 students in it. 3 programmers and two "artists". They broken down into 2 teams: one decided to completely redo the UI (did interviews, user testing, mock-up, a design spec and then implementation and other group decided to add a new texture mapping functionality (research and coded the new feature - made new models and textures for the feature). The UI team was able to contact several members of the original stanford team for advise, feedback and user testing. Both completed there work but did not do enough user debugging and testing to make sure all the bugs were out of their implementations.

 

UI team's resources: a ui designer and two programmers

ui_team_proposal.txt - week 2 proposal

ui_team_report.pdf - week 5 final report

 

Texture team's resources: a programmer and a texture artist

texture_team_proposal.html - week 2 proposal