|
"Pragmatic game development practices for small (and not so small) companies" - Noel Llopis
Pragmatic = Getting things done. Different methodologies have different benefits for different teams. P2G = 2 Man Company.
“Learn from yesterday live for today hope for tomorrow, [...]” (Einstein)
Where do you spend the money? Where it matters. Ie, Monitors. Computers. Games. Not where it doesn’t matter. Ie status symbol chairs and cars. How about expresso machines? If people want to be in the office, then it could be worth it.
Workgroup suits? (Exchange/Lotus Notes? Expensive and difficult to administer. Google Apps is free...)
Build Servers? Recycled PCs. Continuos Integration.
Version control? P4, Subversion, Alienbrain, etc. Pick one that fits your needs & budget. Goal at P2G was “sync and run”.
Leverage Open Source (where license allow).
It’s all about the product? Is what you want to send time on the best for the end product?
Super-Light Agile. If it fits. Cork board + index card task matrix. Considering TDD & PP. (P2G does TDD but not PP). Functional tests test whole systems. Automated functional tests - ie monkey keyboard automation test + input & game state recorder for verifying deterministic logic.
20% rule (google) - employees can use 20% of their time for anything potentially productive (personal projects included). Keeps work fresh & moral high.
Focus on your target platform(s) not “possible” future platforms.
Don’t over engineer. KISS. Fix todays problems today.
Think long and hard about tools. How long will it take to make, and how much time will it save?
Think long and hard about scripting (languages). How long will it take to make, and how much time will it save?
Mentality - Don’t reinvent the wheel. Be aware of your advantages and strengths and make use of them. Pace yourself. A marathon is not a sprint. slides: http://powerof2games.com
|