October 22, 2009

ALM and Legacy SCM Migrations


Application Lifecycle Management (ALM) project objectives often include reducing the number of tools in use, so that there are a smaller number systems to integrate with in order to produce a common view of the status of projects in the application life cycle.

Saving Money is a major change driver these days!
Saving Money is a major change driver these days!

In the current economy, budgets are often tight and always scrutinized. Organizations are looking to reduce the number of tools in use, to reap cost savings and reduce technical administration, logistics, and other costs associated with managing many vendors.

ALM functionality and cost savings ultimately drive organizations to consolidate their legacy SCM systems.  When all teams are using the same CM tool, it is much easier to achieve ALM objectives of providing a consistent, accurate view of project status while promoting common processes.

Legacy SCM consolidation projects have very manageable risks, as they follow well-trodden paths.  Sure, there are lots of things to consider in selecting & implementing a migration strategy.  It's neither trivial nor rocket science, but the desired outcome is easy to visualize.  That makes for a successful project.  Of course, working with someone who's done it before helps mitigate risks.

Following evaluation of the most appropriate enterprise-grade SCM solution (which generally leads people to Perforce), efforts start to move various teams onto the new system, bringing each teams up to par with training and tool-specific best practices education.  Upon completion, various cost savings are realized, but more importantly, the capabilities of the development organization as a whole rise to new levels.