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
That is why I have 3 or sometimes 4 projects on 1 project team, so the leader has some time to prepair his stuff and keep the teams on going. As we speak I am just figuring out what the best setup is.
1 Make a team
2 Make a project and add the teams in it.
3 Develop software and add them for the team.
if this is not working I do not know, its working here on the test build.
I have a leader with HR btw.
Perfect conditions here also and only 2 small projects to handle. Go to the Team menu, then click on employees. Click on the some emplouees and then on details, in the bottem right. If the person is a stress chicken then it might be the problem.
Otherwise I dont know.