bliki: ActivityOriented

Specialization isn’t the problem; organizing along lines of specialization is.

activity-oriented teams are prone to optimize for their own activity and not for the bigger picture of delivering useful software.

Organizing by activity gets in the way of lowering batch size of work that is handed-off between teams.

Software development is an iterative design process. In order to achieve true iteration and realize the value of fast feedback, its activities need to be performed with a single team (having a common reporting line) as far as possible. Many internet business and independent software vendors (ISVs) already operate in this way.