Creative Vision, Cooperation Between Leads and Recruiting What You Aren't A large story-based game project such as an RPG requires several Leads/Coordinators because nobody can be good at everything, and even if you were trying to do all the work yourself would be boring and take a really long time. Xenallure has or will eventually have: - Lead Designer/Team Coordinator (Me) - Lead Writer (Me) - Art Coordinator (Me - I wear lots of hats) - Lead Programmer (?) - Music Coordinator (?) - Lead Animator/Cinematics Director (?) - Playtesting Coordinator (?) - Webmaster (?) So, all the roles I can't fill, I obviously must recruit someone else to fill or they won't get done and we won't have a game. But if I can't do it myself, it's probably because I know next to nothing about it, (*cough*programming*cough*) so how do I know what kind of skills to ask for in my help wanted ad, or how to test if a candidate is qualified? If I want the gameplay to work one way, and the lead programmer wants to program it to work a different way, how can I assess whether there are legitimate technical reasons not to do it the way I want, or whether it is just a matter of personal taste? If I weren't the designer or the writer or the art coordinator I would have exactly the same problems with them. Or what if there's a dispute between, say, the animator who wants 3,000 poly models and the programmer who says the game engine can't handle that, and I don't know anything about either technical issue? I know there are no right answers to these questions, but I will have to recruit a lead programmer in about 2 weeks and I don't have a clue how to go about doing that, so any tips you can have to share will be appreciated.

Here at UTD we have a habit of posting messages all over the place. We have whiteboards in the honors lounge, and more in the arts/tech labs that we use. Found it's a good way to get help in obscure areas. I guess the equivalent here are the forums, but that isn't as helpful as it might seem.

I'm in charge of making a game for the regional museum, and I'm fighting to learn ActionScript, Flash animation, Illustrator, an isometric engine, more about sound effect creation, as well as digitally writing/recording music for the game. The most useful thing I've found is to have at least one person *outside* your group to ask about each area you need help in. I'd suggest PMing the heck out of a few GDNetters who have experience in it.

Be sure to ask for a portfolio from anyone you bring onboard, as this should demonstrate that they have at the least basic competency, and have at least in the past been able to succefully complete at least one project. Try to somehow guage the personality as well - you'll need a team that can get along with each other without significant clashes. They don't all have to be perfectly friendly or anything, but if someone is too difficult to work with, it will cause serious problems.

As Oluseyi said, you'll want to have at least a basic understanding of each and every task that you'll be recruiting people to do - it'll help immensely with effectively communicating ideas, progress, etc, and will also aid you in choosing the correct candidate. If you absolutely cant learn anything about a particular area - say you try to learn a bit about the basics of programming and you just can't seem to get it to 'click' for example - then you should have someone you know well who does understand these areas, and be able to consult with them on things.

Quote:Original post by sunandshadow
Or what if there's a dispute between, say, the animator who wants 3,000 poly models and the programmer who says the game engine can't handle that, and I don't know anything about either technical issue?

A good programmer should be able to give you an explanation of why (s)he is setting out the requirements and/or limitations they are imposing, and similarly, the animator should be able to give you a reason why he wants to use a particular format/poly-count/whatever. With the basic knowledge you really should pick up in each area, and with the explanations you've been given, you should be able to quickly verify that the reasons are legit, and make sense. If both have good, legit reasons, then I'd tend to side with the programmer, but of course, that will be your decision if the situation arises.


While all your programmers (and other staff for that matter) must be good, your lead programmer is probably particularly important - make sure you get someone with a bit of experience, and preferably who's worked with a team (bonus points if they've been lead) in the past. A lead programmer should ideally also have some basic knowledge in various areas by the way.

So basically, my advice is also to try to learn a bit about each and every area - read up a bit, and try out a few basic tasks yourself to get a bit of a handle on the terminology and what's involved, or alternately, as Oluseyi suggested, to find someone else to do so for you (in which case you'd be giving them a fair amount of control over the project however).

Good luck, hope that helps a bit. [smile]

Quote:Original post by Drew_Benton
but if you have any programming specific questions you can feel free to PM me.

Same from me, if you happen to have any questions come up.

Quote:Original post by Drew_Benton
You really need to have a lead programmer that is also a Team Coordinator with you, but on the programming side of things.

...

The way our project works is that we have someone as the manager of the programming and then a manager of the arts and stuff. This way they can work together on what is best, while handling the specifics of each side on their own. I think it's working out good right now [smile]. SO you need to find a complement!

Yeah, this is definitely what I want to do. :) The challenge is to recruit a person like this. o_O

I should probably clarify that I don't have totally zero knowledge of programming, I took a semester of C++ and got a B in it, my final project was an ascii-art mancala game with an AI player. What I meant was more that it's taken me years of studying art and writing and working as a staff artist and writer before I was capable of being a lead for those things, it will take a programmer with that much experience to decide what language/engine Xenallure should use and create a plan for how to program all the various bits and get them to function as a game at a reasonable speed on a wide variety of computers without crashing. And anyone who's competent and experienced enough to do all that and manage a staff of programmers probably already has their own project to work on, or would want more of a say in the game's design than I can give them... :(

These roles have titles.

The "lead programmer" or "program manager" is usually referred to as the Technical Director. The Art Director is the "lead artist".

I assume the Xenallure is a non-commercial/hobbyist company? There's no way that one person can act as the Team Manager (Producer), Lead Designer, Head Writer, and Art Coordinator (Art Director) on a serious project without half-assing a good deal of that along the way.

Quote:Original post by dgaf
These roles have titles.

The "lead programmer" or "program manager" is usually referred to as the Technical Director. The Art Director is the "lead artist".

I assume the Xenallure is a non-commercial/hobbyist company? There's no way that one person can act as the Team Manager (Producer), Lead Designer, Head Writer, and Art Coordinator (Art Director) on a serious project without half-assing a good deal of that along the way.

There's a big difference between an art director and a lead artist. The lead artist is the person who does all the initial sketches and sets the visual style for the game. The art director is the person who gives instructions to artists about what they must create, suggests changes, and collects approved pieces and passes them over to the programming staff to stick in the game or the webmaster to add to the webpage. The first is an artist, the second is a manager of artists and editor of art.

Xenallure is a volunteer project but our goal is to turn out a professional product comparable to a final fantasy game, because several of the staff members are experienced hobbyists ready to turn professional but in need of a good portfolio piece to demonstrate our talents.

I don't want to be in the position of wearing all these hats because I know it takes a lot of time to do a good job at them. It's not too much of an issue yet because we aren't going to switch from the design phase to the production phase for about another month. Meanwhile I am trying to delegate various responsibilities - my goal is to end up as the lead writer and director of everything non-technical, while delegating all other roles to qualified staff. My project last week was to recruit a level/combat system designer and an architectural artist and give them their initial instructions, and I also acquired a potential musician by accident; this week as they start producing I will be helping them get a more pinpointed idea of what we need for the game, while also continuing to guide previously-recruited concept artists through completing various assignments. When the team have gotten oriented enough that they only require a minimum of instruction from me I will work some more on my own tasks (writing mainly) and do a design doc update, hopefully to the point where we will have enough specs to hand to a programmer and enough concept art to make a project webpage - that will be our next milestone. :) Then I'll start over with the next cycle of recruitment and orientation. This process has been working well for me so far - fortunately I have management experience and am the kind of person who enjoys juggling a variety of tasks.

The artists, depending on your project (concept artist, animator, effects artist, environment artist, and modeler) should be getting creative fuel from the designers. Not all companies have a dedicated content designer, and no hobby company should really have a dedicated designer. In a hobby company and even some established companies everyone is sorta a designer. It's silly to think that someone has no good ideas because they know how to program in C++.

It's good your doing something to make this happen. Best way to learn is to jump in and do it :).

Best of luck on your project!