Learning from Postmortems (slides adapted from Michael Mateas)

Slides:



Advertisements
Similar presentations
Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
Advertisements

Systems Development Environment
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
Game Development Essentials An Introduction. Chapter 11 Production & Management developing the process.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
ITEC 370 Lecture 25 Lifecycles. Review Questions? F give prototype demonstration –Testing plan for your software Life cycles –Scrum (Roles, Meetings,
Agile-Scrum in QA – Case study at TraderTools Amitay Itskovitch TraderTools LLC QA Manager Phone: ,
Software Life Cycles ECE 417/617: Elements of Software Engineering
Learning from Postmortems (slides adapted from Michael Mateas) UC Santa Cruz CMPS 171 – Game Design Studio II
Project Work Playtesting + Postmortem. Plan for today Lecture + discussion Groups status report New Features /Changes in game engine LUNCH BREAK Group.
Introduction to UML (slides adapted from Michael Mateas)
Lecture 5 CS171: Game Design Studio 1I UC Santa Cruz School of Engineering 18 Feb 2010.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Lecture 6 CS171: Game Design Studio 1I UC Santa Cruz School of Engineering 23 Feb 2010.
Valve’s Design Process for Creating Half-Life 2  Presented by David Speyrer and Brian Jacobson.
Presentation Outline - Concept Concept Initial Work –Game Design –Initial Prototype Latest Work –Game Refinements –Media Future Plans –Schedule –Final.
FINAL DEMO Apollo Crew, group 3 T SW Development Project.
Michael Burnside Blog: Software Quality Assurance, Quality Engineering, and Web and Mobile Test.
4/23/ :45 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
C O N F I D E N T I A L 22-Oct-15 1 StarCite Engineering Weekly Meeting StarCite Engineering Feb 9, 2009.
strategize We listen and give clients what they really want, without being afraid to express our expert point of view. We are a creative group of professionals.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Phoenix Scrum User Group Simplifying Scrum Online May 21 st 2009.
It’s tough out there … Software delivery challenges.
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
Microsoft Deployment Workshop Deploying Office 2003 Editions Joe Liptrot Linkpad Limited.
Bad Apple Behavior (slides adapted from Michael Mateas) UC Santa Cruz CMPS 171 – Game Design Studio II courses.soe.ucsc.edu/courses/cmps171/Winter12/01.
Fine-Tuning Game Controls UC Santa Cruz CMPS 171 – Game Design Studio II courses.soe.ucsc.edu/courses/cmps171/Winter13/01 8 February 2013.
Game Design Studio III (CMPS 172) Fine-Tuning Game Controls UC Santa Cruz CMPS 172 – Game Design Studio III courses.soe.ucsc.edu/courses/cmps172/Spring12/01.
Taxonomy of Video Game Bugs Based on slides and research originally by Chris Lewis, published at the Foundations of Digital Games 2010 conference UC Santa.
Prototyping UC Santa Cruz CMPS 170 – Game Design Studio I 4 November 2014.
CS 134 Design Documents.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
TK2023 Object-Oriented Software Engineering
Software Development.
UC Santa Cruz CMPS 172 – Game Design Studio III
Agile Metrics that Matter
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Appendix B Agile Methodologies
Managing the Project Lifecycle
Valuable Project Management Tools and Techniques
Reflecting on Sprint 1 Reports
Where Agile Business Meets Agile Development
Game user research in industry Jim Whitehead
Microsoft Ignite /11/2018 1:18 AM BRK4017
Microsoft Ignite /22/2018 3:27 PM BRK2121
T Project Review Group: pdm I2 Iteration
Game playtesting, Gameplay metrics (Based on slides by Michael Mateas, and Chapter 9 (Playtesting) of Game Design Workshop, Tracy Fullerton) UC Santa Cruz.
Journey Postmortem. UC Santa Cruz CMPS 171 – Game Design Studio II
Personal branding. UC Santa Cruz CMPS 171 – Game Design Studio II
Game user research in industry Jim Whitehead
SUCCESS MANTRAS FOR BEING AN EFFECTIVE INFORMATION DEVELOPER IN AGILE
Game Project IMGD 4000 Due Dates: Form Teams Treatment Website
Game Design Practicum (CMPS 179) Summer 2012 Course Overview
UConn’s Web Content Management System
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Software Process Models
Tour VII: Change Management
Adding a Publication Entrepreneurship.
Appendix B Agile Methodologies
Adapting Agile in Pharmaceutical Industries
Implementation and Migrating to iModules
Process Improvement Showcase Information and Template Fall 2019
INTERACTION DESIGN IN PRACTICE
WORKSHOP Establish a Communication and Training Plan
Product Development & Planning
Presentation transcript:

Learning from Postmortems (slides adapted from Michael Mateas) UC Santa Cruz CMPS 171 – Game Design Studio II ejw@cs.ucsc.edu 7 February 2012

Lab Update Chair issue update

Upcoming Events Chelsea Howe: More Than A Feeling: Affective Design and the Future of Games Wednesday, February 8 11am, E2 180 (Simularium) February 28: Visit by Microsoft Studios Game crits by staff from Microsoft Studios Discussion of career opportunities

Upcoming deadlines Thursday: no class Friday (February 10) Jim attending Inside Social Apps event Friday (February 10) Team status reporting Thursday (February 23) Sprint 2 ends Game playtesting plan Web site framework

Postmortems Game postmortems are a regular feature in both Game Developer Magazine and Gamasutra Focus on 5 things that went right, 5 things that went wrong Reading postmortems helps you to recognize good and bad development patterns happening on your own game Doing your own project postmortems solidifies lessons for future projects

What went wrong: testing Not leaving enough time for testing – end up focusing on stability rather than gameplay details of levels and enemies http://www.gamasutra.com/view/feature/4216/postmortem_freeverses_top_gun_.php?page=4 http://www.gamasutra.com/view/feature/4201/postmortem_8monkeys_darkest_of_.php?page=4 Beta too late to have any real impact http://www.gamasutra.com/view/news/24767/The_Game_Developer_Archives_Postmortem_Ensembles_Age_of_Empires.php Insufficient communication between QA and development Didn’t take early advantage of automated testing Testing with the wrong audience http://www.gamasutra.com/view/feature/3939/postmortem_singaporemit_gambits_.php?page=4

What went wrong: design Mistakes in level design Not progressing game mechanics and obstacles along with the story Not adequately melding design styles from multiple designers http://www.gamasutra.com/view/feature/4216/postmortem_freeverses_top_gun_.php?page=4 Design decisions (like temporal variety) that multiply content needs http://www.gamasutra.com/view/feature/4201/postmortem_8monkeys_darkest_of_.php?page=3 Balancing AI quantity (handling many units or characters) and quality (AI looking good when focus is on a single unit) http://www.gamasutra.com/view/feature/4201/postmortem_8monkeys_darkest_of_.php?page=4 Lack of specified design lead to divergent efforts during balancing and tweaks Lack of focus on controls http://www.gamasutra.com/view/news/25950/Postmortem_Behind_The_Scenes_Of_Scribblenauts.php Lack of high-level vision http://www.gamasutra.com/view/news/25517/Postmortem_Behind_The_Making_Of_Sucker_Punchs_Infamous.php http://www.gamasutra.com/view/feature/3339/postmortem_dreamworks_.php?page=3 Overloading player with new concepts and systems http://www.gamasutra.com/view/feature/4010/postmortem_square_enixs_the_.php?print=1

What went right: design Prototyping http://www.gamasutra.com/view/feature/4205/postmortem_twisted_pixels_.php?page=2 http://www.gamasutra.com/view/news/25517/Postmortem_Behind_The_Making_Of_Sucker_Punchs_Infamous.php http://www.gamasutra.com/view/news/25002/InDepth_Inside_The_Making_Of_KingsIsles_Wizard101.php For level-based game, focusing from the beginning on level design http://www.gamasutra.com/view/news/25950/Postmortem_Behind_The_Scenes_Of_Scribblenauts.php Early establishment of physical metrics for player character/world interactions http://www.gamasutra.com/view/feature/4122/postmortem_crystal_dynamics_tomb_.php?page=2 Nailing the gameplay mechanic before content development http://www.gamasutra.com/view/feature/4216/postmortem_freeverses_top_gun_.php?page=2 Playtesting provides feedback on difficulty arc and gameplay and builds a fan community http://www.gamasutra.com/view/feature/4230/postmortem_ronimo_games_swords__.php Sticking with 2D http://www.gamasutra.com/view/feature/3903/postmortem_riverman_medias_.php?page=2 Physics-based gameplay http://www.gamasutra.com/view/feature/3339/postmortem_dreamworks_.php?page=2

What went wrong: project management Grossly underestimating the amount of work http://www.gamasutra.com/view/feature/4230/postmortem_ronimo_games_swords__.php?page=2 http://www.gamasutra.com/view/feature/4122/postmortem_crystal_dynamics_tomb_.php?page=4 School projects versus full development http://www.gamasutra.com/view/feature/4230/postmortem_ronimo_games_swords__.php?page=3 Adding stuff at the last minute Didn’t investigate outsourcing companies sufficiently leading to bad experience http://www.gamasutra.com/view/feature/4205/postmortem_twisted_pixels_.php?page=4 Positive feedback leads to feature creep http://www.gamasutra.com/view/feature/4101/postmortem_ngmocodemiurge_.php?page=4 Crunch http://www.gamasutra.com/view/feature/4041/postmortem_gaijin_games_bittrip_.php?page=3 Inadequate analysis and planning for technical risk http://www.gamasutra.com/view/feature/3804/postmortem_brothers_in_arms_.php?page=4

What went right: project management SCRUM http://www.gamasutra.com/view/news/25799/Postmortem_Behind_The_Scenes_Of_Brutal_Legend.php http://www.gamasutra.com/view/feature/3804/postmortem_brothers_in_arms_.php?page=2 Internal art person had great art community connections, leading to good outsourcing experience http://www.gamasutra.com/view/feature/4201/postmortem_8monkeys_darkest_of_.php Empowering creativity across the team http://www.gamasutra.com/view/news/22710/InDepth_Behind_The_Scenes_Of_Far_Cry_2.php

What went wrong: tools and tech Networking code started too late http://www.gamasutra.com/view/feature/4205/postmortem_twisted_pixels_.php?page=3 The lure of shared technology http://www.gamasutra.com/view/feature/4122/postmortem_crystal_dynamics_tomb_.php?page=2 Loosing iterative design time due to refactoring http://www.gamasutra.com/view/feature/4122/postmortem_crystal_dynamics_tomb_.php?page=3 Inefficient art pipeline http://www.gamasutra.com/view/feature/4101/postmortem_ngmocodemiurge_.php?page=3 Custom tech (driven by unique gameplay features) leading to inefficiencies (“transformation tech too expensive”) http://www.gamasutra.com/view/feature/3910/postmortem_american_mcgees_grimm.php?page=5 Physics problems http://www.gamasutra.com/view/feature/3339/postmortem_dreamworks_.php?page=3

What went right: tools and tech Successfully building on tools from last project http://www.gamasutra.com/view/feature/4205/postmortem_twisted_pixels_.php Custom engine supported experimentation and fast turnaround http://www.gamasutra.com/view/feature/4201/postmortem_8monkeys_darkest_of_.php?page=2 Using an existing, well-established engine allowed focus on design http://www.gamasutra.com/view/feature/4188/postmortem_wadjet_eyes_the_.php Good use of middleware http://www.gamasutra.com/view/feature/3910/postmortem_american_mcgees_grimm.php?page=3