Project management and layout with pseudo code

Hi Guys
I wanted to do a little research around game development for indie games.

When you start a project what do you focus on first? User controls, gameplay elements, Asset functionality, maps??

Basically I just want to know generally in phases what usually happens during game development?
How do you go about managing your projects and citical components that have to be done before the next component begins?

Oh and about the pseudo code, what are you guys using to draw up your theory as a reference guide? The senior dev at work (C#,SQL,etc) says he uses UML editor or something like that.

The process always depends on the size of the team (e.g a team with 6 people can work on the gameplay + the meshes at the same time). I do it like that (main steps) :slight_smile:

  1. planning everything ^^
  2. creating the basic gameplay elements (running, walking, crouching, jumping,…) -> because we need those stuff for our map
  3. creating meshes + particles + sounds -> we will need them for the map + gameplay
  4. do the level design + overwork your gameplay stuff + create needed meshes

First is the design. Then I almost always do the very hardest thing first. It depends on team size. An example would be, a game has a unique game mechanic that requires using the Kinect to position some in-game item. I would probably do first, just the piece with the Kinect as the first programming task.