Hello all,
I have been working on a game and brought a few others in on it to develop it and make content. The team is currently unpaid (will be compensated after release/funding)
In this setting, what do you think are some good practices to follow to make the project a success and a good development environment?
The project is still early in development and I would consider this to be my first leading role in something like this
Managing vs Leading:
As I am pretty directly involved in the development of things, from story to design to actual coding, I have tried to steer clear of 'managing', or over-managing as its a small team and nobody is seeing the $$$ to put up with much BS.
I think I have mostly done this with some success, but it has made it difficult for me at times. I have tried taking less of the front seat and letting everyone pedal as well, but I found that people didn't really have much drive to contribute anything unless it was adding to something that I created or was already there.
So far I have created a wiki, a forum, a Google drive, and set up some other tools for the team, as well as a Facebook page and have managed the security of our information (like making everything non-public)
Legal stuff - NDA/other agreements:
When is the best time to do the formalities and write up things like NDA's and other agreements to protect the project? Gauging my team as it is, I think they would not be keen on signing things like this - it seems to be a big turn-off when I start talking about rules and organization. I can understand the reticence as it is unpaid, but it also seems very risky in thinking of the future. I have already had a developer leave the project, and I have yet to see if problems are going to arise from this.
I know these types of things are very standard for larger projects with funding, but it seems difficult to implement in this setting. I have read many stories of failed games due to petty internal conflicts, developers retracting their contributions, misappropriated funding, and dissatisfied developers that probably could have been prevented if everyone had some type of written, formal agreement adhering to some rules of conduct.
I dont see agreements and NDA's as an attempt to disadvantage people or deprive them of freedom, but as something to protect the project as a whole - which is bigger than any one person and affects everyone.
Is it a good idea to put write something up and get some signatures? If so, when is a good time and what would be the best approach (as far as selling it to the team)? Should any agreement be very light and plain, or well written and very detailed?
↧