Question about teams, roles and skill stars

[ralfaltmann]

Hi,

I don't understand the game mechanic regarding teams, roles and skill stars. If I'm correct, somewhere in the tutorial it's mentioned that a worker with the lowest star rating affects the progress.

Here are a few questions:
1) let's say I have one team with six designers and six programmers. This wouldn't be good because in the design phase the programmers would slow down the design process, and in the development phase it's the same because of the designers slowing down the development, right? Instead, I should use two separate teams. This sounds logical to me and it's my typical team setup.

2) Now, let's take the skill stars into the formula. If the above is right (employee with lowest skill star affects progress), does it mean I need several teams of programmers, designers, etc all with their own team specialisation? How do 0-star and 1-star specialisations like system, 2D, etc. affect the progress of e.g. 3-star team members? For example, a design team with three members, were one has 3 stars in system, one has 3 stars in 2D and one has 3 stars in network. How do the other two with 0 stars in a given specialisation affect the team?

3) Next is the employee role: since I use dedicated teams for designing, developing, support, etc. I usually don't assign special roles - so the support team members are also allowed to be programmers (which is good for bug fixing), and also marketing team members are also allowed to be programmers (which shouldn't matter, they'd never be given a development task). So, is role assignment a thing to dig deeper into?

Regards

[VayneVerso]

Hopping on this thread, because I'd also like a little more clarity on it. Seems weird that an entire project would get dragged down just because you've got one newbie on the team. I mean, yes--the project should take longer than if you had a seasoned vet there instead, but it shouldn't slow down your other developers *that* much except, maybe, in the bug fixing stage, because they've got to fix all the mistakes the new guy made.

[DailyDoseOfStress]

I am actually going to be making a video on that and will be partially explained in part 2 of my hard mode series. If you guys like I can post a link to the first part here and you can save the playlist and follow along too if you want.

https://www.youtube.com/watch?v=bY4iwiQm_kg

[DailyDoseOfStress]

Number 1

So as far as development, its marginal, both teams that designed said product, 1 with mixed ratings 1 2 and 3 star designers as oppose to a team with 3 3 star designers, it was developed a month earlier and released a month earlier. Both were outstanding products, and each team iterated 4 times.

Number 2

A team member with 0 stars will not work on anything until they are educated in that category. So if you have in your instance, 3 designers: System, 2D, and Network only those categories will be worked on. However, once you train (Educate) an employee, for example, the one with System 3 stars on a 1 Star 2D, then that employee will help (Contribute) to the project. So if you don't want them doing 1 star work then don't educate them in that category. (This is confirmed, as long as you dont assign them a secondary role)

Number 3

Role selection just kind of rounds out a teams ability to do certain jobs. It just comes down to personal preference, but to hit on number 2, only give them what you want them to do.

[VayneVerso]

Thanks for testing that, TSF. That's very useful information.

[DailyDoseOfStress]

Absolutely. I enjoy the hell out of this game.

Originally posted by TheWatcherUatu:

Thanks for testing that, TSF. That's very useful information.