Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Best planning for game developing

Discussion in 'General Discussion' started by Deleted User, Jan 15, 2015.

  1. Deleted User

    Deleted User

    Guest

    Hello!!

    I'm starting a big game project and need some management tips. we are in two programmers and one designer. is practically our first project in games. then we don't know how to divide tasks or where to start. you have any tips that can help us?
     
  2. Xaron

    Xaron

    Joined:
    Nov 15, 2012
    Posts:
    368
    Yes. Start smaller. It's really that easy! I mean I was in the same boat. My first idea for my first game was the next gen MMORPG. Many have been through this. I learned pretty fast that it's simply not practical to start game dev with a big one. After that I practiced with much smaller games. After doing 7 simple games I do now my first bigger one.

    Generally break down a big task in many smaller ones where you can make time estimations. Set milestones for your team - again, small ones.
     
    Kiwasi and Deleted User like this.
  3. kalamona

    kalamona

    Joined:
    Aug 16, 2011
    Posts:
    727

    Extra Credits' advices to game dev beginners.
     
    peteorstrike, Aurore and Deleted User like this.
  4. Deleted User

    Deleted User

    Guest

    Nice Xaron! thanks!
     
  5. imaginaryhuman

    imaginaryhuman

    Joined:
    Mar 21, 2010
    Posts:
    5,834
    What I'm doing is a) making game design document including most of the design/creative decisions having been made up-front, with a fair amount of detail, covering everything in the finished product. b) then breaking that down into a fairly extensive list of tasks that actually need to be done to implement it. c) time estimate of each tasks... aim for tasks no shorter than about an hour to avoid too much detail, avoid trying to figure out how code works at this point. d) following the task plan and implementing each part. This is mainly per the `indie developers survival guide` book.
     
    Deleted User likes this.
  6. Kiwasi

    Kiwasi

    Joined:
    Dec 5, 2013
    Posts:
    16,860
    Build and deploy a small game first. I'm talking a few weeks or a month at most. This will let you experiance the entire project timeline. And it won't matter too much if you stuff it up.

    Then it's just a matter of repeating the same tasks on a bigger scale.
     
    Deleted User likes this.
  7. wccrawford

    wccrawford

    Joined:
    Sep 30, 2011
    Posts:
    2,039
    Maybe not quite the same, but it's certainly the right first step towards it. :)
     
    Deleted User and Kiwasi like this.
  8. Kiwasi

    Kiwasi

    Joined:
    Dec 5, 2013
    Posts:
    16,860
    Totally true. But it will solve the "Where do I Start?" problem. Maybe not with the exact right answer, but with one close enough.
     
    wccrawford and Deleted User like this.
  9. Deleted User

    Deleted User

    Guest

    Aewsome! thanks for the tips everone!