John Daniel Fletcher
@johndanielfletcher
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.
Specialization isn’t the problem; organizing along lines of specialization is.
Software development is an iterative design process. In order to achieve true iteration and realize the value of fast feedback, its activities need to