Advisor

Feature vs. Component Teams

Posted August 6, 2009 | Technology |
Jim Highsmith
Recently, looking at scaling issues for a couple of multinational organizations, the issue of feature teams (customer-oriented) versus component teams (technically oriented) arose again. There are some in the agile community who think that feature-oriented teams are the only correct way, but the issue is more complicated than a simple solution can handle. For software systems that run into millions of lines of code and large legacy systems for which the architecture can't be easily changed, a combined team strategy is often warranted.
About The Author
Jim Highsmith
Jim Highsmith is a Cutter Fellow Emeritus. He was the founding Director of Cutter’s Agile Product & Project Management practice and received the 2005 Stevens Award in recognition of his work in adaptive software development and Agile processes. Mr. Highsmith has 30-plus years’ experience as an IT manager, product manager, project manager, consultant, and software developer. He has consulted with IT and product development organizations and… Read More
Don’t have a login? Make one! It’s free and gives you access to all Cutter research.