Green Lighting Meeting Other Documentation:
ð Feature List/GDD/ Product Backlog: a copy of whatever format the current design documentation is in.
Concept Design Document
ð The Big Picture:
o Describe the primary gameplay experience a player will have
o Who is the intended audience?
o Explain why the intended target audience will want to play it.
o Explain how this game fulfills the Product Owner's mandate/Research Goals.
ð Risks (Identify areas of risk.)
o What are your technical risks? What parts of your design do you not understand how to implement, or expect problems with implementing?
o What are your design risks? Do you have an innovative type of gameplay that might not be fun?
o Do you have a backup plan for your each of your serious risks? How would they affect your game?
o Risk management: how will you know when to switch to a backup plan?
ð Innovation
o What does your game do that others don't?
o What is the area of innovation?
o What evidence do you have that you are innovative?
ð Conception:
o Story Development (if necessary)
o Setting
o Characters (if any)
o Tone/feeling
ð Core Gameplay
o Verbs (Actions taken by player)
o Key Game Mechanics (what happens in the game, and why?)
o Dynamics
o Aesthetics
ð Scope
o Can this project be completed by the end of the summer? Why?
ð Release Standards
o Intended Platform (Windows XP, Vista, Mac OS , Distribute over Web, etc.)
o Expected size of download:
o Expected size of footprint of game on HardDrive Green Lighting Meeting, Page 2 Comments:
Approvals:
Product Owner Signoff:____________________________________
GAMBIT Signoff:_________________________________________
MS 1: First Runnable Checklist Wednesday, June 24thDocumentation:
ð Current version of GDD.
ð Current version of Art Style Guide/Current Concept Art. ð Current version of Tech Guide: list at least intended game engine and any 3rd party code/libraries the team intends to use. Functionality:
ð Proof of game engine: Program runs, using the team's chosen game engine and libraries.
ð Display of working art pipeline: Displays a piece of art, provided by the team's artists
ð Display of working audio pipeline: Plays a sound, provided by the audio team.
ð Display working input code: Game must take inputs from the player, and change something on the screen based on those inputs.
ð User must be able to choose to exit the program, and the program must exit successfully. ð QA Lead serves as Release Engineer: QA Lead should both make and release this build, and serve as release engineer for the team for all subsequent releases. Comments:
Approvals:
QA Signoff:____________________________________
GAMBIT Signoff:________________________________ MS 2: First Playable Checklist Wednesday, July 1st Documentation
ð Current version of GDD or product backlog/sprint tasklist - whatever the team feels best documents their game.
ð Current Art Asset list
ð Current Audio Asset list
ð List of implemented gameplay features.
ð List of current Risks
ð QA Checklist 1: should cover all features and assets implemented, should also include all core mechanics.
Functionality
ð User can start the game
ð User can play through an entire game.
ð User can exit the game.
ð Runs and quits without crashing.
ð If game can be paused, it can be continued.
Look And Feel
ð Visuals
ð Art assets are in where they should be.
ð Audio
ð Audio assets are in where they should be.
ð Sound effects play on cue.
ð Music soundtracks play and loop correctly.
ð Genre
ð Overall genre and intention of the game is apparent to user.
Comments:
Approvals:
QA Signoff:____________________________________
GAMBIT Signoff:________________________________
MS 3: Usability Review Thursday, July 9th Documentation
ð Current version of GDD or product backlog/sprint tasklist
ð Art Asset list
ð Audio Asset list
ð List of implemented gameplay features.
ð List of remaining Risks
ð QA Checklist: Implemented features (mechanics and screens), assets, and usability
Basic Game Functionality
ð Game runs from an independently installed executable.
ð Game runs on a system without any developer tools installed.
ð User can play through an entire game.
ð When game is over, it returns the user to the Main Menu.
ð User can tell when the game is over, and in what state it ended in (win, loss, other.)
ð User can exit the game.
ð Runs and quits without crashing.
ð Game can be paused and continued.
ð Operating Systems it works on: ________________
ð Size of download: ________________ (if relevant)
ð Game size on harddrive: _________ (if relevant)
Look and Feel
ð Visual
ð At least placeholder art in all places requiring art.
ð Audio
ð Sound effects play on cue
ð Music plays and loops correctly
ð Any dialogue/speech is in (may be placeholder.)
ð There is sound - may be placeholder - in all locations the game expects to have sound.
Screens/Menus
ð All screens are in, with full functionality. (All buttons work; all screen and game inter-connectivity is in; controls have visual and audio feedback.)
ð Art on screens may be rough/work-in-progress.
ð Installer: has MIT acceptable EULA.
ð Splash Screens (GAMBIT, 3rd party Logos, Team Logo)
ð Menu Menu/Title Screen
ð Options Screen (if present)
ð Credits Screen (GAMBIT standard, and Team)
ð Win/Loss screens (if present)
ð Pause Screen (or some indication game is paused)
ð Pop-Ups (if any are intended.)
UI
ð HUD/Screen Display
ð All on-screen HUD elements are present (Health bars, Points, Etc.)
ð It is clear to users what the elements are for, and what they mean.
ð Elements give appropriate visual/audio feedback when updating.
ð User Controls: Overall
ð There is a consistent and usable control scheme. (IE: the same style of keys/commands are used to play the game and to navigate through the game.)
ð Player controls give useful visual feedback
ð Player controls give useful audio feedback.
ð User Feedback
ð It is visually clear when a button is selected (but not yet Used.)
ð It is visually clear when a button/command is used.
ð All actions that can have clear audio feedback.
Comments:
APPROVED BY:
QA:__________________________________________
GAMBIT Staff:_______________________________________
MS 4: Beta (Feature Complete) Thursday, July 23thDocumentation
ð List of implemented features
ð Backlog/task list of any outstanding work.
ð Set of QA checklists: feature checklist, compatibility checklist.
Basic Game Functionality
ð Game passes its QA checklists
ð Game runs from an independently installed executable.
ð Game runs on a system without any developer tools installed.
ð User can play through an entire game.
ð All features are implemented and usable.
ð When game is over, it returns the user to the Main Menu.
ð User can exit the game.
ð Runs and quits without crashing.
ð Game can be paused and continued.
ð Operating Systems it works on: ________________
ð Size of download: ________________
ð Game size on harddrive: __________
Look and Feel
ð Visual
ð No default fonts.
ð No placeholder art - all art assets are in.
ð Audio
ð Sound effects play on cue
ð Music plays and loops correctly
ð All dialogue/speech is in.
ð All sound is in game, and is in final polished form.
Screens/Menus
ð All screens are in, with full functionality. (All buttons work; all screen and game inter-connectivity is in; controls have visual and audio feedback.)
ð Legal
§ EULA must be accepted by user if anything is downloaded (a .exe or an installer.)
§ EULA must be linked on the web page for web-playable games.
§ MIT Copyright notice must be present in game, on Title, Main Menu, or Credits screen.
ð Installer: (if present!)
ð Installs to an acceptable default directory
ð Allows the user to choose which directory to install to.
ð Splash Screens (GAMBIT, 3rd party Logos, Team Logo)
ð Credits Screen (GAMBIT standard, and Team)
ð Menu Menu/Title Screen
ð Optional screens
ð Options Screen
ð Win/Loss screens
ð Pause Screen
ð Pop-Ups
UI
ð HUD/Screen Display
ð All on-screen HUD elements are present (Health bars, Points, Etc.)
ð It is clear to users what the elements are for, and what they mean.
ð Elements give appropriate visual/audio feedback when updating.
ð User Controls: Overall
ð There is a consistent and usable control scheme.
ð Player controls give useful visual feedback
ð Player controls give useful audio feedback.
ð User Feedback
ð It is visually clear when a button is selected (but not yet Used.)
ð It is visually clear when a button/command is used.
ð All actions that can have clear audio feedback.
APPROVED BY:
QA:__________________________________________
GAMBIT Staff:_________________________________
MS 5: Gold Certification Friday, July 31 - Aug 5thDocumentation
ð List of implemented features.
ð Installation Directions
ð Web-Blurb: Description of game for potential players - No more than 200 words.
ð Complete Internal QA Checklist set: Features, Assets, Compatibility
Installation:
ð Game runs from an independently downloaded executable
-OR-
ð Game runs in a browser
-Or-
ð Game gets installed from an independently downloaded installer
o Game installs to an acceptable default directory.
o Game allows user to choose installation directory
ð Game runs on a system without any developer tools installed.
Legal
ð EULA is accepted if anything is downloaded.
ð EULA is
ð MIT Copyright is present on one of: GAMBIT Splash, Main Menu, Credits.
Basic Functionality
ð User can play through an entire game.
ð All features are fully implemented.
ð Game passes its internal QA checklists.
ð When game is over, it returns the user to the Main Menu, or otherwise indicates to the user that the game is over.
ð User can exit the game.
ð Runs and quits without crashing.
ð Game can be paused and continued.
ð Operating Systems it works on: ________________
ð Size of download: ________________
ð Game size on harddrive: __________
Look and Feel
ð Visual
ð No default fonts.
ð No placeholder art - all art assets are in, and in final polished form.
ð Audio
ð Sound effects play on cue
ð Music plays and loops correctly
ð All dialogue/speech is in.
ð All sound is in game, and is in final polished form.
ð No placeholder sound.
Screens/Menus
ð All screens are in, with full functionality and final art.
ð Splash Screens (GAMBIT, 3rd party Logos, Team Logo)
ð Menu Menu/Title Screen
ð Options Screen (if present)
ð Credits Screen (GAMBIT standard, and Team)
ð Optional Screens
§ Options Screen
§ Win/Loss screens
§ Pause Screen
§ Pop-Ups
UI
ð HUD/Screen Display
ð All on-screen HUD elements are present (Health bars, Points, Etc.)
ð It is clear to users what the elements are for, and what they mean.
ð Elements give appropriate visual/audio feedback when updating.
ð User Controls: Overall
ð There is a consistent and usable control scheme.
ð Player controls give useful visual feedback
ð Player controls give useful audio feedback.
ð User Feedback
ð It is visually clear when a button is selected (but not yet Used.)
ð It is visually clear when a button/command is used.
ð All actions that can have clear audio feedback.
Comments:
APPROVED BY:
QA:__________________________________________
GAMBIT Staff:_____________________________________
MS 6: Marketing Materials August 6th
Documents
ð Poster art.
ð 10 uncompressed, full resolution screenshots in .png format.
ð Full resolution video of 2 full playthroughs of the game: one successful and one unsuccessful
ð Game description: 200 word description of the game. (Think of it as a marketing ad, to convince people to download your game and give it a try.)
ð Installation instructions: no more than 1000 words. Needs to include instructions and links for any additional plug-ins or downloads the player may require.
ð Blog post about the game to go along with the game's release on the web - can be about the game, making the game, the process of development, whatever is relevant.
ð Any original art created, including paper prototypes. All materials creaed should be organized and collaged for the GAMBIT staff to store.
|