SCM: Keeping your teams in sync
Have best practices, will success
Changes are happening faster than ever before. The challenge to keep pace with these changes has become tighter than ever—SCMs had better evolved into something responsive to this degree of dynamism.
Poole recalls one of the first tools, called the SCCS, or Source Code Control System, saying while most of the SCM tools in the market today share the same underlying data model of SCCS, they were fine 30 years ago.
“But it hasn’t kept pace with all the changes since then,” he says, referring to the changes as the introduction of the Internet, distributed development, outsourcing, among others.
“The market expectation is that they can get the changes they want faster than ever before,” Poole says. “Some of the changes that have come in that time are faster operation, virtual file system, web interface, peer-to-peer infrastructure, replication, transactions (sometimes called change sets), change packages, and streams.”
Could integrating SCM best practices into the tool address the issue?
Let’s take a look at the best practices AccuRev’s SCM: “built-in advanced parallel development capabilities that scale with your team’s changing business requirements, enabling you to realize the most appropriate development process for these requirements.”
Users of AccuRev have successfully implemented Agile methodologies, optimal SCM patterns, and other processes without constraints or unnecessary costs. Common tasks such as code reviews, nightly builds, refactoring, merging changes from release to release, and fast comparison and differencing are greatly simplified in the AccuRev software.
Email This Article
Print This Article
