Download to read offline
Uploaded byChristopher Totten
"You Made a Game, Now What?" Week2 game production methods and realities
The document discusses various game production methods, including waterfall, agile, and scrum, outlining their processes, pros, and cons. It emphasizes the importance of iteration, playtesting, and collaboration among team members for effective game development. Additionally, it highlights roles within the game industry and considerations regarding team size and project duration.
More Related Content
Similar to "You Made a Game, Now What?" Week2 game production methods and realities
More from Christopher Totten
"You Made a Game, Now What?" Week2 game production methods and realities
- 1. GAME PRODUCTION METHODS ANDREALITIES
- 2. TOPICS • Iteration • Productionmethods • Waterfall • Agile • Scrum • Game production misconceptions • Roles in the game industry – and what happens when your team is too small to have them
- 3.
- 4. ITERATION • Initial plan 1.Conceptualize 2. Design/implement 3. Test 4. Evaluate results of test 5. Back to step 1
- 6. CONCEPTUALIZE/IDENTIFY • Design documentation •“One sheet” • Concept art • “Elevator pitch” • Market research/comparable games • Technology proposal • Marketing proposal
- 7. DESIGN/IMPLEMENT • Paper prototype •Individual game mechanic tests • “Test scene” in your game project • Gray box • “Programmer graphics” • Start simple and small, get increasingly complex as you finalize individual pieces
- 8. TEST/CONSTRUCT • Playtest • Allthe time • No really • With strangers • Anybody who isn’t someone working on the game • Take notes • Respond to feedback TRENDS, not individual ideas (unless they’re really good)
- 9. EVALUATE RESULTS OFTESTS • Documentation helps you remember what you learned • Take time to meet with your team and evaluate your playtest notes • Should be introspective enough so that the next “conceptualize” phase can be well-informed
- 10. DEVELOPMENT STRUCTURES • Waterfall •Agile • Scrum
- 11. WATERFALL • A linearprocess where steps are not moved on to until the current step is finalized/verified • Steps • Software and system requirements – product requirements doc • Analysis – Models, schema, and business rules • Design – software architecture • Coding – proving and integration • Testing – debugging • Operation – release, support, maintenance
- 12. WATERFALL • Pros • Problemsare researched early • More time/money spent laying a good foundation for the project than trouble-shooting later • Structured, good for projects where there are a lot of “knowns” • Cons • Does not iterate • There are not always a lot of “knowns” in projects
- 13. AGILE 1. Our highestpriority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7. Working software is the primary measure of progress. 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility. 10. Simplicity — the art of maximizing the amount of work not done — is essential. 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- 15.
- 16.
- 17.
- 18. SCRUM • Product backlog •Wishlist of features or elements created by product owner • Sprint backlog • Feature pulled from product backlog to be worked on my the team • Sprint • Set of time (day or week) to accomplish an amount of work • Daily scrum • Meeting to check in and keep moving forward • Ship the increment • Scrum review to review process • Retrospective on the product/experience
- 20. WHAT DOES PROJECT DURATIONMATTER?
- 21. WHAT DOES TEAM SIZEMATTER?
- 22.
- 23.
- 24.
- 25. ROLES • Programming • Design •Producing • Graphics • Sound • Marketing • Licensing & new business • Testing • Hardware engineer • Executives • Writers
- 26. ROLES…ARE NICE WHENYOUR STUDIO IS BIG ENOUGH