Sunday, 8 February 2009

Business rules for developing Games

Why use a game project triangle

Game project triangle is critical to identifying, on why make the game and what goals are for the game. The project triangle helps manage the particular project and its challenges. Having a triangle can keep the team flexible and decisions can be made, whether the game is going to be on budget, on time or high quality. The project triangle can also help with identify restrictions, requirements and act as a genuine opportunity to shape a successful vision of the game.

Question to answer for current game

What are you trying to accomplish?
I had this idea of making a horror FPS game and I’m trying to accomplish a game that is on time and high quality.

- When must you complete this game project?
- The game must be complete by March 20th, but unlike a real game project I can’t go over my time limit.

- How much money do you have to produce it?
- Apart from buying the software game engine, not much.

- Who do you have to get the job done?
- No one, but myself.

How to achieve an ultra-low budget game

The game project may take a long time, 500 to 1000 hours plus, so it may be a good idea to share the project with other, like friends, family and even like mind individuals over the internet. Producing a low budget game will result in a small simple game, but playable and would require a minimum of engineering to get it functional.
Working on an existing game and create a mod, is another way of creating an ultra-low budget game.

Primary, secondary and tertiary feature

Primary feature are the preproduction of the game and tasks that have been slit-up, for the team to perform, within a given time.

Secondary feature are the building of the game, taking the ideas and features of the primary and make them into finished items.

Tertiary features are after the game ships, which may involve coming back to the secondary features and improving and changing them through patches.

Using Primary, secondary and tertiary feature can support a development team, as a method of measuring progress and task completion that enable the highest quality workflows. Setting up the features by prioritizing the features into three different categories, will make the team members cruise through their tasks with confidence, feeling like winners and making progress quicker.

No comments: