I worked in an automotive project where we switched from "subsystem teams" to "feature teams" organization structure in the middle. On the requirements and sys

I worked in an automotive project where we switched from "subsystem teams" to "feature teams" organization structure in the middle. On the requirements and system test level, it was a clear advantage. For the implementation it was a mess because where we had clear owners previously, it was now a lot of discussion who should be responsible for maintenance. From Jan Bosch, I heared the proposal to have "component owners" in addition to "feature teams". They are senior developers, normal members of feature teams, and explicitly responsible for specific components. This means they should review all code changes from any team but not do any functional changes themselves (as long as they wear the "component owner" hat), just maintenance. This might work. (Unfortunately, he hasn't published this idea anywhere yet. It was an internal talk which I cannot share.)