Agile SCM gives software project managers and integrators the ownership and control over the higher level aspects of the environment such as component structures, creation of activities, assigning activities and most importantly the selective control over
integration of activities and subsequent baselines.
The Agile SCM architecture is designed to meet the following two main objectives:
- From the developers' perspective, they are assigned items of work (activities) for which code changes are made via any Subversion interface (command line, Tortoise, Eclipse). Each activity is isolated on a self-contained subversion branch and the state of the activity is recorded via
a simple set of 'state transitions'.
- From the Integration Manager's perspective, the activity state can be managed and reported against and, when appropriate, integrated into a project integration branch.