Source control best practices for teams with multiple projects

Damon Young — Thu, 10 Apr 2008 14:08:00 -0500

While we're very big proponents of Subversion here at ProjectLocker, we also recognize that even the best tools and, consequently, the teams that use them can be crippled by the wrong development processes. With that in mind, here is an excellent article by Henrik Kniberg, a Certified Scrum Master with Crisp, a Stockholm-based Agile consulting firm. In it, he proposes a methodology to most effectively make use of your version control tool when applying Agile best practices in an environment with multiple & distinct teams working from common code base. Notice that he never mentions a specific version control tool, just a set of procedures and team protocols to help optimize the process. More details at the link below:

"Version Control for Multiple Agile Teams"

Watch this blog for more posts in the future on best practices and other development resources we think will help you build better software.

ProjectLocker Blog: Tag best

Source control best practices for teams with multiple projects