Feature Teams vs Component Teams in Product Development
A lot has been written and said about comparisons between feature teams and component teams, and their respective pros & cons in software development. It has been a topic of debate in many product organizations, whether they are just starting or are in the middle of their Agile adoption journeys.
I will attempt to highlight some of the differences between the ways of working in these two types of teams through the story of a fictional bank called, Macdroid Bank. This bank has recently acquired a digital banking license, and is now building a mobile application for its customers. I will play this story in two scenarios, one where the bank has decided to use feature teams, and the other where they have a component team model.
Scenario 1: Macdroid Bank has multiple feature teams; each working on end-to-end customer-centric features. One of the feature teams is ‘Team MaxBizValue’. It has a mix of people who used to belong to different projects, working on different technologies and applications in the old Waterfall era of the bank.
Scenario 2: Macdroid Bank has multiple component teams; each working on a specific component that requires expertise in skills/technology used for that component. One of the component teams is ‘Team MinBizValue’. It specializes in working on mobile applications, with no…
