First Time Working Together

Oct 24, 2009

Breadth of Skills is Useful…

I’m an advocate for solo game development. I encourage developing a breadth of skills. I think it’s helpful for every game developer to have at least a little comfort and fluency in the tools needed for art, sound, and programming. This improves communication. This creates respect between people with different strengths. This increases freedom to develop your own ideas. This accelerates team projects by removing bottlenecks.

…But No Substitute for Teamwork

That said, strengths vary.

Knowing how to use Photoshop or 3D Studio doesn’t mean someone is a good artist. Knowing a programming language doesn’t mean someone is a capable programmer. Knowing how to use Fruity Loops doesn’t make someone a talented musician.

Even if you can do all of those things very well, there are still advantages to working with others. Different artists do different types of art well, and learning to work with an artist other than yourself makes it possible to develop games with any type of art, depending upon which artist you work with. Different programmers enjoy different types of problem spaces, whether artificial intelligence or online multiplayer or distinctive graphics tricks. Learning to work with someone else means who you work with next can greatly vary the types of videogames you make, avoiding a creative rut.

Team members can help to keep one another on track. Much like having a partner for workouts, studying, or joining a club.

Teamwork also builds your future network. Networking with beginners may not sound like a strategy for future success, but they’ll be tomorrow’s experienced developers.

Connections can make a big difference.

Challenges of Team Forming

Finding a team can be hard. When your passion exceeds your experience, it’s hard to get the attention of an established team.

Making the problem even more challenging is that, without prior experience, it can be tricky to tell passion on track for success from passion on track for disaster. Everyone has ideas, and everyone has good intentions.

Just a few minutes of feedback from an experienced friend might be able to save months of trouble, or steer a team clear of a known causes of project dissolution.

Minimal Team

  • One programmer. More programmers can actually slow things down on a beginning project, due to the complexity of code integration, and the added communication overhead.

  • One or more digital artist. Beginner game art mixes easier than beginner game programming.

  • One audio person. This is often either the programmer or artist on double duty, hunting for creative commons and public domain audio.

  • One of the above, with an additional interest in the videogame’s design, or possibly a level/puzzle designer if the genre needs a lot of that type of content.

  • Someone with at least a few finished projects, able to meet a few times over the life of the project, in order to help the developers steer clear of avoidable trouble.

Altogether: 2-3 people. Having that third to provide audio support, additional art, or additional puzzles and levels can be helpful. If you can find an experienced advisor to touch base with a few times over the life of the project, that’s also smart thing to do.

Free Team Building Assistance

If there’s already a club of interested videogame developers in your area that you have access to, I’d suggest joining in with them. If you’re in a situation to found a new organization of that sort, check out the next section in this month’s Free Lessons for some tips and tricks to help increase the chances of success. If you’re like most people, and you have neither easy access to a videogame development club nor a situation in which it could make sense for you to found such an organization, I’d like to help.

You’re reading this section, probably, because you have some experience in at least one of the areas needed for game making (programming, art, audio), and you’re ready to translate those skills into videogame making without starting from scratch in the other skills. I recently put out a call to some of the project leaders that had successfully completed projects with the Game Creation Society, to see who would volunteer to fill that experienced advisor position. I have five people willing, supporting up to six teams, since I’ll be volunteering for this effort, too.

Apply for Match-Making and Support

Please e-mail please e-mail cdgdl.free@gmail.com (this is a different e-mail address than used elsewhere on my sites) providing the following information. Maximum 2 sentences each.

  1. Which of the following do you have experience in that you are willing to handle for the project: programming, art, audio (sfx/music), level/puzzle design

  2. What genre(s) are you most interested in working on?

  3. Are there any genre(s) that you would not consider working on?

  4. Are you committed to working with your teammates for free, to create a videogame to be shared publically for free, in the interest of advancing the portfolio and experience of everyone on your team? (1 word answer, yes only)

  5. Would you like to have an experienced advisor provide feedback at the beginning, middle, and near-completion phases of your project? (1 word answer, yes/no)

  6. What is your current background or experience in videogame making skills?

  7. Links to any site(s) with your past or present creative or programming work. Please do not send attachments. If you don’t have this yet, that’s ok!

These questions are not to judge you. These questions are not because I’m asking you to prove yourself (although practice doing that is a good life skill). These questions are strictly because the short answers to them will help me pair you effectively with team mates that have similar interest, similar experience, and, only if you’re interested, with an advisor that has relevant experience.

To be clear, the volunteering advisor would not serve any sort of management, directing, or authoritative role. They would be there strictly to offer advice from experience on a few limited occasions, which you could then ignore or interpret as you see fit.

I am offering this completely for free. No strings attached, no selling of your information to anyone else, and no promotions or spam. I like helping people – a clear extension of what GameDevLessons.com and these Free Lessons files are all about. If you have friends that would find this sort of assistance useful, please let them know about it!

It may take awhile for responses to be collected, matched, and selected by the volunteer advisors. I’ll do my best to reply to every inquiry. If I can’t match you with an advisor, I’ll at least try to match you up with others with common interests around your skill level as soon as suitable matches become available.

It can only help. E-mail cdgdl.free@gmail.com.

(Originally posted as GameDevLessons.com Vol. 7 Sec. 1)

Este artículo está disponible en español. Traducción por cortesía de Andrés de Pedro.

Comments are closed.

All contents Copyright ©2012 Chris DeLeon, solely to prevent others from copyrighting it.
Permission to reproduce, modify, and distribute this content granted without special request.

Site production by Ryan Burrell.