PSM-I · Question #122
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…
The correct answer is 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. 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…
Question
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.)
Options
- AYou cannot do Scrum without feature teams.
- BProductivity may suffer when making this kind of move.
- CGetting support from the business side first helps.
- DFeature teams have less communication overhead.
- EWith feature teams, it is easier to calculate the productivity per team.
How the community answered
(27 responses)- A30% (8)
- B48% (13)
- E22% (6)
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.
Topics
Community Discussion
No community discussion yet for this question.