8. Production Plan
The production plan is an organization document that will help us to create a gold version of our game Fantasy Brawl before June the 12th. We will be using a Gantt Chart to organize our deliveries as well as Trello to manage each milestone.
This Gantt chart represents the tasks that are needed to be done for each delivery. Each team member is responsible for one or more tasks, respecting their roles.
Concept Discovery All the technical information is gathered and published in the Wiki of our repository.
Vertical Slice In this basic prototype of the game, we will have 4 players but only one character available for playing. The character will have basic movement with gamepad and will have a basic ability and a special one. We will have some basic UI.
Alpha We will have a game menu, with improved UI art and audio. There are 4 characters now instead of only one. All the game mechanics are ready to play even if they are not polished.
Gold Game polished and ready to be delivered. Bugs fixed, mechanics, art and audio is polished.
Concept Discovery All the technical information is gathered and published in the Wiki of our repository.
Vertical Slice For the vertical slice we had one map with one character that had a basic attack, a special ability and a shield. There was a split screen for 4 players and a storm that damaged the players. Basis music and audio and really raw UI and menu screens. Players can play through gamepad.
Alpha For the alpha we improved all the UI, added 3 more characters with their respective basic attacks and special abilities. We did not add more maps but improved the map that we had for the vertical slice. Changed the champion selection screens, the menu and added a map preview.
Gold Solved bugs, created website, improved UI and art, added more abilities to the characters, set up a control menu where players can change their gamepad setup.
The task assignment and management was done thanks to trello tool. We used it for each milestone to register and assign specific tasks to each team member and registered the time estimations for each tasks there.
For a more detailed view of the tasks done by each member, the time estimation and the deviation we created an excel table to make the information more organized and visual.
List with possible risks and contingency methods we will use to avoid it.
| Risk | Contingency |
|---|---|
| Team member missing a meeting | If possible, reschedule the meeting for as soon as possible or upload all the information talked about in the meeting so it is available for all the members of the team. |
| Personal Issues that impede a player to help the team | Get to know what the member was responsible for and divide the work into the other members |
| No gamepads available for testing | Each team member will have to bring his gamepad every day of testing |
| Game lasts too much | Balance damage, reorganize map, to make the game last less |
| A character is not fun to play | Change the character abilities to make it more fun and test again. |
Our team met every Wednesday to organize the work and see how is the development is going. During the meetings we shared the work done by each member, discussed possible new ideas, improvements, problems we had and possible problems that we could have in the future. Some of the information from the meetings was recorded on Word documents.
We did additional meetings before each important delivery to prepare the presentations and to make sure everything was going according to plan.