Rational Team Concert and Rational Team Concert source control have been designed with teams in mind. But teams are made up of individuals, and there are many ways that an individual can benefit from using Rational Team Concert source control on a development effort that has no other contributors. By checking in Eclipse projects to a repository workspace, organizing them into components, and creating streams that represent specific states of component development, you can back up your work and have access to every version of it. You can also become familiar with those Rational Team Concert source control operations that handle the fundamental tasks of storing and retrieving versions of files and folders, comparing one version with another, and preserving "interesting" configurations (ones that are known to work, for example, or ones that exhibit a specific problem or other characteristic that needs attention). All of these operations will also be part of your work with a team.
Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug