To culminate our posts about the Game Outcomes Project, we're including a self reflection tool the project posted to help you predict the success of your own program, using the data and metrics accumulated from surveying hundreds of game developers. It comes as a downloadable Excel sheet, and is as easy as answering 38 questions.
We've been spending some time talking about the Game Outcomes Project this week, which surveyed hundreds of game developers to come up with empirical data and weigh several factors against success indicators. The previous instalments have been a bit negative in tone - moreso a "what not to do" - whereas this one will be all about what good teams do right.
We've been focusing on the Game Outcomes Project this week, which surveyed hundreds of developers about various factors in their completed projects, and weighed them against multiple indicators of success. In the third part of the published series, the project talks about a hot-button issue: Crunch.
As part of the Game Outcomes Project, developers were surveyed about conditions in their workplaces for completed projects in game creation. Part two of the project's published analysis looks at regular dysfunctions that teams have, as understood by management theory, and aspects around teamwork have a very clear positive correlation with success.
Starting in October of 2014, a group of statisticians have been analysing one of the biggest surveys of the game development industry ever undertaken. After putting elements like Agile, Scrum, and Waterfall, as well as various financial incentive schemes under the microscope, the extent to which they affect the final product might surprise you.
