• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (3)

1 localhost commented Permalink


2 localhost commented Permalink

With this model, who is responsible for development tasks that cross teams such as the build, config mgmt., a DAL or needs that arise from the architectural team? Does the responsibility just fall on any one of the teams? <div>&nbsp;</div> Have you ever seen a model where one team is dedicated to common development needs while the other teams focus on building subsystems of functionality?

3 localhost commented Permalink

When you start introducing separate teams such as this you run the risk of increasing bureaucracy because these separate teams will start to suboptimize on their specialty. On the other hand you could improve efficiency because these subteams could address those issues much better than having all the development teams trying to do so. Build/integration is a common example as discussed in point 8 above.<div>&nbsp;</div> The point is that you need to make the right trade-offs for the situation that you find yourself in.

Add a Comment Add a Comment