Arrr-chitecting Games and Game Teams
summary
Pirate crews codify governance: crews of ~150–200 elect an elected captain (battle authority) and a quartermaster (operational authority), sign written articles of agreement that set pay shares (most get 1, captain and quartermaster 2), onboard procedures, and injury compensation (e.g. 800/1,000-pound payouts for lost limbs). They use the Jolly Roger as a marketing tool, adapt roles like sailing master and carpenter, and their systems actually increase surrender rates and operational efficiency rather than chaos.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 1:03Pirates and team dynamics
- 3:55Why pirate talk accepted
- 9:54Pirate history
- 17:19Pirate crew organization
- 24:45Pirate democracy
- 30:55Pirate efficiency and marketing
- 34:07Pirate leadership diversity
- 37:59Task allocation and HR
- 42:08Key takeaways
- 45:43Rethinking game dev teams
- 47:33Questions and answers
related talks
47mCo-operative Game Development
28mCooperative Economics for Engineers
18mCare and Craft in Teams - Keeping People Motivated
49mAll Aboard: Tools and Tactics for Building Team Consensus.
22mHow to create agile teams and foster the culture of excellence while developing games
52mBuilding Game Studios that Last
16mThe MIT Sailing System
46mBuilding memorable software engineering teams