Rapid, iterative prototyping best practices

Rapid, IterativePrototyping Best Practices

What were gonna cover Who I am Why you should prototype 8 rules for how to do it right 8 tricky pitfalls to watch out for Q+A, contact info

Who I am 2008

Fire Hose Prototyping Early Prototype 2009

Fire Hose PrototypingMarch 15th April 14th June 16th April 1st May 14th July 20th

Fire Hose Prototyping Early Prototype 2010

Fire Hose Prototyping Early Prototype (Michael Bay Version) 2011

Fire Hose Prototyping

Why Prototype? Prototyping ≠ Pre-Production Prototyping Vertical Slice  Pre-Production Production

Why Prototype?

What does it get you?• Leads to stronger design, aesthetic, mechanics• Allows you to try potentially great ideas you can’t waste time on during development• Lets you identify and bail on bad ideas sooner• Lets you make costly mistakes up front, when they are easier and cheaper to fix• You’ll learn how to talk about your game

When NOT to Prototype?

So how do you do it?

1. Set aside ~1/3 of dev time

2. Put together a crack team

2. Put together a crack team Dance Central Go Home Dinosaurs Artist 1 Artist 2 Artist 1 Artist 2 (Models + (Animator + (Models + (Animator + Textures) Rigger) Textures) Rigger) Coder 1 Coder 2 Coder 1Designer Producer Designer Designer Prouducer Prouducer Dancer Choreographer

3. Get the right tools

4. Tools and peopleshould match the risk

5. Don’t fear the trash can

6. Add features, test ideas, cut content

7. User Test! A lot!

8. Keep itloose, embrace change

The How, Recapped1. Spend ~33% of dev time on prototyping2. Assemble a small, crack team that works together well3. Use simple, fast, easily understood tools4. Team ability should match riskiest parts5. Be ready to throw out prototypes for the sake of iteration6. Work on features and ideas, not content7. User test constantly and incorporate feedback8. Dont get bogged down with documentation or overhead

The Tricky Bits

9. Be on the lookout for “surprise fun”

10. Deciding when to iterate

10. When to iterateMarch 15th April 14th June 16th April 1st May 14th July 20th

11. Dovetailing with marketing and PRSmall Companies Big Companies

12. Using deadlines

13. Beware ofBallooning Scope

14. Ping-Ponging back and forth

15. Knowing when to stop prototyping

16. Anger whenprototypes get canned

Tricky Bits, Recapped9. Watch out for “Surprise Fun”10. Iterate regularly and/or when necessary11. Dovetail prototyping with PR + Marketing if possible12. Deadlines are your friend, use em!13. Keep the prototype small, dont let scope balloon14. Dont iterate back and forth without forward movement15. Stop prototyping when you have a vertical slice16. Manage expectations well so if you have to can aprototype the team doesnt rage

Contact Info, Q+A Eitan Glinert (give me a 5 star evaluation!) eitan@firehosegames.com www.firehosegames.com

http://www.firehosegames.com	2779
http://10.3.10.155	26
http://10.3.10.84	22
http://hardlightwiki	10
http://hl-wiki	9
http://stgwiki	9
http://translate.googleusercontent.com	4
https://twitter.com	4
http://webcache.googleusercontent.com	1
http://firehoseart3-pc	1

Rapid, iterative prototyping best practices

by firehosegames

Accessibility

Categories

Upload Details

Usage Rights

10 Embeds 2,865

Statistics

Rapid, iterative prototyping best practices Presentation Transcript