Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
There are alot of factors wich work into there.
remember raise priority level up to 10
Your workers are probably not sufficiently trained in ALL aspects of the 2D editor. This was the pitfall in my first couple games. Make sure the programmers are trained as much as possible in System and 2D code. I believe you just hired some guys with System specialization and very low 2D coding skills, so when the System part of the 2D editor was done, they could only continue with 2D that they are not competent in. Hence the slowdown. Training is very important.
Whenever starting a new project, you can check out on the software design document window on a pie chart the importance of each skill. There you can also see the optimal team size (broken down into programmer, artist, designer categories) and you should compare that to your current team setup (having much more than the recommended size actually slows down development).
Quick question, when you say the right team size - even if I put MORE people on the team it will hinder the progress??
e.g. If recommended team size is 3 programmers, but I put 5 on it then that will actually slow progress down compared to if I only put the 3 recommended programmers.
If this is the case, do you find that you are constantly creating new teams and rearranging people depending on the software you're creating to match the size of the recommended project?
Yes, using more than the recommend amount will hinder progress and slow everything down.
Since i usally realese an bunch of Software at once (OS<2D/3D-Editor, Game Engine etc), i have one large team for the OS (actually 2, since i achso have one for Modded Motherboards), one medium and 1-2 small once. Usally i only have to change the medium team, in that case i put the best of of an small team into there (or vice versa). For all other cases, Products usally will need more employees with each Generation, so adding one isn't that of an problem, since it will rather happen every 2 Generations, since sequals with their boost achso reduce the amount of
employees needed.
Thanks for the explanation - I've been mainly doing deals / contracts to get the hang of it, just designing my 2nd product (antivirus) and put together a small team for it, actually I think I added one to many, so will need to remove one - Back on support he goes !