Co-Development: From the other side
summary
Claims that build and protect trust is the single most important resource, backed by real fixes: removing management and letting two developers talk face to face rescued a stalled feature; culture mapping and direct developer-to-developer handovers repeat across projects. Start with small tasks, keep promised senior people, and treat the first delivery as make-or-break — one case saw a vendor promise 100 devs then deliver 15 (later 45). Company scale examples: 500/300 distributed teams, current studio ~70. Start small and overdeliver.
AI-written summary · about
chapters (4)
related talks
30mWorking with Independent Developers: Lessons Learned Over the Years
22mHow to create agile teams and foster the culture of excellence while developing games
50mDeveloper Experience in Mobile GameDev: How We Rebuilt a Plane in Flight
50mThe Challenges & Advantages of Creating a Game Remotely
32mHow Your Players Can Make You A Better Developer
34mGame Developers Are Becoming Directors, Not Coders
47mMaintaining development costs while meeting the growing expectations of consumers
59mUnsaved Progress Will Be Lost: Why the Game Industry Forgot How to Make Games, and How to Fix It