hawthorne to gamasutra - yow! conferences€¦ · dev beck the rise of open source scrum agile...
TRANSCRIPT
1
2
3
4http://www.gamefaqs.com/sinclair/948634-the-hobbit/faqs/14842
5
6
7
8
9
10
11
12
13
14
http://www.library.hbs.edu/hc/hawthorne/09.html and
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2464836/
15
16
17
18
19@ghammadi
20
21
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.
23
“What prevents us from
‘Getting Shit Done’ is the
last time we got shit done.”
http://techblog.realestate.com.au/getting-shit-done/
24
25
26