Comments on: SCM Team Collaboration http://accurev.com/blog/2007/10/26/scm-team-collaboration/ SCM and Agile Software Development Blog Wed, 09 May 2012 07:08:34 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Chris Boran http://accurev.com/blog/2007/10/26/scm-team-collaboration/comment-page-1/#comment-348 Chris Boran Fri, 26 Oct 2007 20:00:56 +0000 http://accurev.wordpress.com/2007/10/26/scm-team-collaboration/#comment-348 We make extensive use of scenario #2 - I personally find #1 to be only marginally useful, and then only on very rare occasions. I suggest that people actually take a more holistic view of their projects - instead of thinking of 'files', think about your features only. Files are just containers that code happens to live in, and can occasionally be quite fluid. Anytime that we have features that integrate more than incidentally with one another (or 'depend on' each other), then we always setup integration streams for the projects to share code between. This way the two feature building teams (regardless of size) can integrate with each other in a sandbox that only effects themselves, and only expose the rest of the organisation to the changes AFTER all the kinks are worked out. We make extensive use of scenario #2 – I personally find #1 to be only marginally useful, and then only on very rare occasions.

I suggest that people actually take a more holistic view of their projects – instead of thinking of ‘files’, think about your features only. Files are just containers that code happens to live in, and can occasionally be quite fluid.

Anytime that we have features that integrate more than incidentally with one another (or ‘depend on’ each other), then we always setup integration streams for the projects to share code between.

This way the two feature building teams (regardless of size) can integrate with each other in a sandbox that only effects themselves, and only expose the rest of the organisation to the changes AFTER all the kinks are worked out.

]]>