❗Why do we need feature teams in Agile?
Usually, traditional companies are breaking down their products into logical pieces of work i.e components and relevant specialized teams. Although this sounds like a natural division, it can bring to a lot of issues when dealing with product/team dependencies or providing business value.
On the other side, we in the Agile world suggest a division into feature teams based on product features, which solve user needs, eliminate the hassle between teams and increase focus on delivering business value. Slicing of user stories vertically makes sure that teams would work on all layers of the feature and have something "potentially releasable" at the end of the work.
Very often, feature teams complain that being far from same-field specialists decrease their knowledge sharing and professional growth as no one has enough time to go to another team and give feedback for example on new technologies or code quality, etc. If the teams are small, the absence of one specialist can affect heavily on the productivity of the whole team.
What kind of challenges do you have when forming feature teams?
Feature Teams
23.09.2020
Articles