[The GIGGAS]

Quote: Originally Posted by RiderGH

Nice article Mike! Im wondering, it would seem like a bigger development team = less "innovation" based on what your saying since it seems like a development team can get crowded quickly. Is that right? Like it seems like when determining what actually "goes into the next game", a lot of people are there with in put, and a smaller dev team would be able to centralize ideas and essentially "get to work sonner" and with a more direct objective.

If I were to make a guess, I'd say that the direct objective is determined before any programmer/artists are brought in. In my head, I see it like this:

people like Ian meet with higher ups who determine the big plan
Ian meets with workers, informs them of the plan
the workers suggest features
Ian and the higher ups decide what gets cut and what doesn't, based on the budgeting idea

So I don't know how big of an issue a large development team is on the planning side. I don't have any experience of that, seeing as the NCAA credits has more names than the building access internal page of my company (or at least, I assume so).