The agile recommendation is to make it easy for everyone to build the system at the push of a button. This saves time:
- It frees programmers from repetitive and mundane tasks
- Reduces time spent chasing down compilation and convergence issues
- Reduces dependencies and bottlenecks, as people won’t get called back to fix the build
A presentation and demonstration of a continuous integration framework at the recent BCS CMSG event demonstrated the advantages:
- Improving quality due to much more immediate feedback of integration problems
- Improved speed as it is done so often, problems don’t lurk unnoticed
Manage Your Test Data
There are various methods for doing this, including one called ObjectMother. If you have any form of database, then you will need to address this issue. The pain of updating a test database to reflect the production database tends to increase the likelihood that they will drift out of sync, thus leading to a variety of errors that really should be caught much earlier. The SCM implication is simply that test data and the resulting frameworks need to be version-controlled along with the code.
Embrace Collective Ownership
Collective ownership both reduces the risk of the key team member falling under the bus while also improving quality through practices such as paired programming. It diffuses knowledge throughout the team and avoids isolated silos of knowledge.
This may also encourage a matching SCM attitude that everybody does SCM on a project. Thus, the SCM person needs to become a focused contributor to the team rather than an enforcer. (S)He should not just do SCM, but also code, etc.
In our experience, this makes for a more enjoyable job, but we've come across quite a few SCM people who like to sit in their \dungeons making occasional forays out to frighten the natives a bit. Being "in the trenches" will also highlight the appropriate automation necessary to make things faster and easier.
Another related aspect of this is the need for the team to become fully conversant with SCM and comfortable with their tool and how to do things like branching and merging, which many are somewhat reluctant to do. Perhaps this is due to too many bad experiences in the past. This is where we can break down some of the barriers between SCM and development.