A Primer on the Game Development Process: The Philippine Experience (2010)
0 likes62 views
The document outlines the game development process, including stages such as concept design, development, testing, and release. It emphasizes the importance of defining target audiences, selecting appropriate platforms, and managing project budgets and timelines. Additionally, it discusses the roles of developers, publishers, and distributors in the game development value chain.
A Primer on the Game Development Process: The Philippine Experience (2010)
- 1. Cesar S. Tolentino August 7, 2010 Manila, Philippines
- 2. The Game Development Value Chain DEVELOPERS PUBLISHERS DISTRIBUTORS RETAILERS GAMERS Much like a mini-Hollywood !
- 3. The Game Development Process CONCEPT DESIGN PROTOTYPE PROGRAM DEV’T ART & MUSIC DESIGN TESTING RELEASE & MAINTENANCE What is now outsourced to the Philippines
- 4. Steps on Game Development 1. Develop Game Concept 2. Choose Target Audience 3. Choose Game Platform 4. Define Game Design Parameters 5. Map Out Calendar with Milestones 6. Create Project Plan Document 7. Quantify Budget 8. Form/Select Development Team 9. Contract Services of Development Team 10. Track Progress and Completion 11. Monitor Quality 12. Confirm Completion and Turnover of Finished Product
- 5. Develop Game Concept 1. Describe Game Theme 2. Describe Characters 3. Define Role of Player 4. Describe Win/Reward Condition 5. Describe Challenges for Player 6. Enumerate Number of Levels/Challenges (optional) 7. Define Length of Game Experience (optional) 8. Enumerate Game Extras (optional)
- 6. Choose Target Audience 1. Age 2. Gender 3. Profession (if applicable) 4. Culture and Religion (optional) 5. Lifestyle (description) 6. Brand preferences (optional)
- 7. Choose Game Platform Options include 1. PC 2. Mobile 3. Portable (Nintendo DS, PSP, iPhone, iPad) 4. Console (Xbox, Playstation, Nintendo Wii) 5. Online 6. Mini-game/Casual game downloads 7. Social networking game (ex., Farmville)
- 8. Game Design Parameters Technical considerations include 1. Programming language to use 2. Technologies to be used (engines, payment portals, chat applications, network management for multiplayer functionality, etc.) 3. Server requirements (if applicable) 4. Internet access for online, multiplayer functionality (if applicable)
- 9. Map Out Calendar Making sure the calendar indicates milestones for 1. Concept design and character design 2. Storyboard(if applicable) 3. Completion of game art and art assets 4. Completion of gameplay programming 5. Completion of animated sequences (if applicable) 6. Completion of sound production 7. Completion of user interface design 8. Game prototyping 9. Game completion and integration 10. Game testing 11. Completion of marketing materials and customer support systems
- 10. Project Plan Document Making sure the Project Plan includes 1. Game Concept Summary 2. Target Audience Description 3. Game Platform Selected 4. Game Design Parameters 5. Calendar with Milestones
- 11. Quantify Budget Make sure the Budget is based on the following parameters 1. Sufficient to cover Scope of Project (refer to Project Plan) 2. Alignment with Milestones (for Budget Disbursements on a Per Tranche Basis) 3. Allows for Contingencies outside of Project Plan 4. Allows for Financial Risk due to project delays and for Project Resets due to problems encountered with technologies selected
- 12. Form/Select Development Team 1. Decide whether to develop in-house or outsource 2. If outsource, Define selection criteria Short-list vendors Select vendor via use of criteria using an evaluation committee 3. If in-house, Better to hire a top-level game designer and allow him/her to form his/her team Better to have a mix of full-time and freelance personnel
- 13. Contract Services of Development Team 1. Prepare airtight contracts first before finalizing deal with vendors 2. Ensure the Project Plan with Milestones is enforceable in the contract, including ensuring there is sufficient provisions for monitoring progress and quality, quantifying standards of progress and quality, elaborating penalties for negative variances, and rewards for positive variances
- 14. Track Progress and Completion 1. Ensure the Project progress and quality monitoring system is accessible to top management in key milestones (minimum of once a week for short- term projects, and once a month for long-term projects) 2. Ensure there is at least weekly progress and quality check reports 3. Ensure there is a measurable point of project completion, with a well-defined process for the submission/turnover of the finished product to a key individual (turnkey approach)
- 15. Monitor Quality 1. Ensure quality monitoring includes product testing at key stages, with the objective of testing playability 2. Ensure there is a system in place for implementing Project Plan changes in scope if there is failure in product quality as approved/certified by top management 3. Observe a gatekeeper approach to final game testing (product is not released if quality failure is imminent or detected)
- 16. Confirm Completion and Turnover 1. Assign beforehand the identity of person who will receive the finished product from the vendor (game developer) 2. Observe a turnkey approach to finished product turnover (with sign off from both the vendor and the Project Owner/Publisher)
- 17. Thank You!