These Guildhall grads decide to build themselves a studio. Check out the benefits of working as one unified team in this blog.
During Guildhall's TGP2, a cohort divides up into small teams to create a CTF mod for UDK.
Cohort 19 was divided up into 5 teams of nine students (one team had eight students). Typically, these teams would setup their team meeting space in a cramped study corale or in a classroom that offers little personal space.
A fellow production student and I are producers for two teams each (four teams total). We realized that these teams were going to encounter very similar problems when learning UDK throughout this TGP. What if we were able to share information across teams and help them learn the editor as a cohort rather than individual teams? Rather than solve the same problem four different times, we could solve the same problem once and disseminate that information across other teams.
We got permission to use a defunct mocap studio on the first floor of the building. That is, if we were able to find enough furniture to house thirty-eight students in the same space.
We made it happen and our four teams volunteered to try out the new studio experience. Here are the perks of going with the studio feel vs. individual team rooms:
Information Sharing
Faster Learning
Less Ramp-Up time
Quicker bug resolution
Underpromise, Overdeliver
The game's are closer to Vertical Slice than Proof of Tech (at the proof of tech milestone).
Cohort Cohesion
It's one big family and it's awesome. This will help the entire cohort as they move forward into their capstone project.
Here are the before and after pics:
Before
Setting up the Studio
A few tables so far
Setting up the Studio 2
Torrent Pod is setup and working
Mushees Pod
Sharing is Caring
You May Also Like
.png?width=300&auto=webp&quality=80&disable=upscale)
