Which of the following is a disadvantage of having a feature team as opposed to component teams?

Having a feature team offers a holistic approach to delivering functionality, as this team takes responsibility for delivering a complete feature from end to end, encompassing all necessary skills and expertise. However, a potential disadvantage is the temptation to build everything from scratch. This happens because feature teams often aim for maximum autonomy and ownership of the features they develop. They may decide to create new solutions rather than leveraging existing components or services that could facilitate quicker delivery and reduce redundancy.

While the tendency to build from scratch can foster innovation, it may also lead to inefficiencies, increased development time, and potential inconsistencies across the product if there is no strategic oversight regarding reusability of existing components. This mindset can undermine the benefits of component reuse, which is a significant advantage in component teams where specialists can optimize for reusability and maintainability.

This understanding illuminates the dynamics of how feature teams operate compared to component teams and highlights the need for a balance between innovation and leveraging existing code or solutions.