SLIDE 1
1
2
1 2 3 - - PowerPoint PPT Presentation
1 2 3 - - PowerPoint PPT Presentation
1 2 3 http://www.gamefaqs.com/sinclair/948634-the-hobbit/faqs/14842 4 5 6 7 8 9 10 11 12 13 http://www.library.hbs.edu/hc/hawthorne/09.html and http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2464836/ 14 15 16 17 18 @ghammadi 19
SLIDE 2
SLIDE 3
3
SLIDE 4
4
http://www.gamefaqs.com/sinclair/948634-the-hobbit/faqs/14842
SLIDE 5
5
SLIDE 6
6
SLIDE 7
7
SLIDE 8
8
SLIDE 9
9
SLIDE 10
10
SLIDE 11
11
SLIDE 12
12
SLIDE 13
13
SLIDE 14
14
http://www.library.hbs.edu/hc/hawthorne/09.html and http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2464836/
SLIDE 15
15
SLIDE 16
16
SLIDE 17
17
SLIDE 18
18
SLIDE 19
19
@ghammadi
SLIDE 20
20
SLIDE 21
21
SLIDE 22
22
Conclusions of the Game Outcomes Project
1. Incentives don’t really correlate with success. 2. Production methodologies don’t correlate with success, but having shared approach does. 3. Project duration has a negative correlation to success 4. Team experience level strongly correlates with success. 5. Team stability correlates with success. 6. Crunch kills quality and success. 7. There is no sure-fire genre, and no sure-fire platform. Re-using the last platform barely correlates to success. 8. Team size makes no difference. 9. Clarity of vision for the game is critical to success.
- 10. Clarity of team structure is critical to success.
- 11. Team trust and psychological safety are critical.
- 12. Great teams estimate with skill.
- 13. Great teams deal with politics and HR issues themselves.
- 14. Great teams use code review and pair programming.
SLIDE 23
23
“What prevents us from ‘Getting Shit Done’ is the last time we got shit done.”
http://techblog.realestate.com.au/getting-shit-done/
SLIDE 24
24
SLIDE 25
25
SLIDE 26
26