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
Second Question: The recommend team size shows how many workers AT ALL are ideal, so you got 3 times as much as you need. As of the Tutorial: "More Workers don't neccesary increase development speed, but might even slow it down" (don't quote me there, but it means the same). Achso, when creating a sequel to a product with the same features, those will be developed faster.
For 2nd question i understand the more ppl may delay the process but when i have ideal number off ppl working the software it takes around 10 yrs instead of 2 like its suppose too. I'm just trying to shuffle things around and see what might work the best. But i'm really intrested to know how does one produce a good OS system in a matter of a month i just dont see that possible?
Another thing is that the estimated time isn't good at all. I usally get outstanding product 3 times faster than it says. It achso depends on your current teams choosen , so it usally shows based on my design team, with no influence of my actuall programmer team (above is even with programmers involved)
And the thing with messages even after porting seems to be just a bug, porting after a product looses its "fame", just won't let it make more sells