Version Control for Multiple Agile Teams
Thursday, April 17th, 2008If you’re developing software using Scrum or XP (or your individual collection of tools and processes) in multiple teams, make sure that you read this article “Version Control for Multiple Agile Teams” about how version control, trunks, branches and policies could be implemented. This is the depicted summary of the great article.
A key lesson that I took from it is that it’s a must to have feature teams. Spanning features (user stories) over multiple teams immediately breaks the pattern, because you not only need to sync each work branch with the trunk, but also sync all work branches that work on the same feature. Given you have n teams, you see that you multiply the need for synchronization from n to n*(n-1) in the worst case.
