If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...
If you have a not-so-usual solution for your problems but need to justify it to your boss...
If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...
...then 'No Bugs' Hare on Soft.ware might be the right place for you.
Your mileage may vary. Batteries not included

Different teams use very different development processes, with very different results.

IT Hares have collectively spent quite a bit of time developing in small- and medium-sized teams, and are ready to share their own experiences with different development processes.

Development Processes, page 1:

BDT – Automating Your Application Testing in Behavior-Driven Way

Quote: “Descriptive style takes its roots from the «chain» pattern, in which the methods enclosed in classes return some reference on themselves.”
Another Quote: “Business-driven testing or BDT allows non-technical members of any development team a stronger involvement in the development process by allowing them to comprehend test cases and even create their own. “
[]

Choosing Version Control System for MOG development

Quote: “For game development (and unlike most of other software development projects), you’re likely to have binary files which need to be edited (representing so-called “assets”)”
Another Quote: “for open-source games, Git does have a Very Significant Advantage™”
[]

DevOps for MOGs

Quote: “This communication channel (coming from Operations back to Development) is extremely important to have a game which is able to work anywhere-reliably in the real world”
Another Quote: “Most importantly, our processes should allow these different production cycles to co-exist.”
[]