What are three things to consider when deciding to move away from such component teams toward feature teams?

Currently, your Development Teams are organized to address a single layer only (for example, front end, middle tier, back end, and interfaces).

What are three things to consider when deciding to move away from such component teams toward feature teams? (Choose three.)
A . You cannot do Scrum without feature teams.
B . Productivity may suffer when making this kind of move.
C . Getting support from the business side first helps.
D . Feature teams have less communication overhead.
E . With feature teams, it is easier to calculate the productivity per team.

View Answer

Answer: B,C,D

Explanation:

The correct answers are B, C, and D, because moving away from component teams toward feature teams may involve some challenges and trade-offs. Productivity may suffer when making this kind of move, as teams need to learn new skills, coordinate with other teams, and deal with legacy code. Getting support from the business side first helps, as they can provide the vision, value, and feedback for the features. Feature teams have less communication overhead, as they can deliver end-to-end functionality without depending on other teams.

Reference: [Suggested Reading for Professional Scrum Master™ I]