Rational Team Concert installs the necessary code, templates, team members, and roles and gives you an out-of-the-box project. The Team Artifacts view contains a very important collection of project items.

Repository Connections gives you a list of currently connected repositories. You can get server information such as Server name, edition, build ID, and license type. Other information such as username, password, and URL for the team server is available. Client access license is also mentioned in the Repository Connections. In general, this section gives you an overview of the server connection, client license, and login credentials.

The Project Section contains the defined Builds, Plans, Source Control, and Work items related to that specific project. You can request new builds, view the old builds, define the build definitions, and build engines. Sprint and release planning is an integral part of the Team Artifacts. You can get a complete picture of the open and completed tasks.

The Source Control section in Team Artifacts has all components of the project and the association of the components to several streams.

In any traditional project considerable time is spent in work planning and issue management by team leads and team members. It could be bugs, enhancements, or new features, but without an integrated solution with the development environment, you spend time on referring the disconnected systems of the development environment and issue/bug management tools. You can take advantage of the pre-defined work item queries and use the shared queries from your project team. Depending on the process template you use, Rational Team Concert knows a variety of work item types such as bugs, enhancements, tasks, and user stories.

The next thing we want to do is to create the Repository Workspace and import the code into the Rational Team Concert client. Go to JUnit Project | Project Area | Source Control | JUnit, right click and select New | Repository Workspace.

Enter the name you desire and description of the project in the dialog and click Next.

Select the workspace visibility depending on your project needs and click Next.

In the next step, select the available components of the project that interests you (as shown next). By default, the Load repository workspace after creation is checked. This means once the Repository Workspace is added, the code for the respective components will also be loaded. In this case, you can see the imported code in the project explorer of Rational Team Concert's client.

Once the Workspace Repository is created, various components are loaded. There are different options to load the Repository Workspace; for now select the Find and load Eclipse projects to add the projects to the client, as seen next.

The "load" action invokes a wizard that gives you a choice to select how to load the projects. The root component has three Eclipse projects that we can load by selecting Find and load Eclipse projects from the wizard.

In the next page, select the projects that you want to import. Optionally select the directory location of the source code to be imported, as shown next:

You can browse the source code from package explorer of Rational Team Concert's client, as in the following screenshot:

Now we can explore the JUnit Project plans. From the team artifacts view, go to various Sprint and Release plans. Sprint backlog shows a list of all tasks for each team member, along with each task's status (open versus completed). A Release backlog shows all the sprints for that release and a high-level view of the task status:

Team Collaboration being perhaps the most important feature of Rational Team Concert, the client provides a way to see and subscribe to the news feeds that let you know everything happening in your project. The news feeds gives you a good platform to understand who is doing what, on a regular basis. All the information regarding the team changes, builds, and plans are tracked and stored for future reference. These feeds can be added to your favorites, and you use the URL of the feed to publish and follow from other websites.

The My Work view is the most commonly used view for a team member. This view shows work items that are assigned to you in several categories. Inbox section has the work items that are recently assigned to you. These work items must be processed to keep them either in the Current Work or Future Work section. The Current Work section contains work items that belong to current iteration. These items must be arranged and planned in the order of completion. Future Work section includes all open, closed, and unplanned work items for the future iterations, as shown next:

The Team Central view includes multiple sections that help you as a team member to have a transparency over the project development. This view has news feeds, build updates, open items in graphical representation, new unassigned work items, and team load. You get a real time view of the project load on various team members as seen in the following screenshot:

You normally attach a process template when a project area is created. Process template is a guide and compass for the process followed in the project. Rational Team Concert provides set of templates for common processes such as Scrum, OpenUP, Cloudburst, and SimpleTeam process. Process Template view contains set of templates deployed in that Jazz repository as shown next:

Rational Team Concert integrates the team into the project and development environment. The Eclipse client enables you to view and manage the users for a project. Along with assigning the users, you can also assign the roles for each user in that project. Remember that each user can have one or more project roles, such as team member, stakeholder, Scrum master, and product owner. The project roles very much depend on the process template that we choose. In our case, these roles result from the Scrum template.

Ideally, you can add another team member for development team and assign role. From the Team Organization view, select the Team Area and open it. In the Team Area editor, you can add a team member and assign appropriate roles. However, because this JUnit Project is a read-only demo, we cannot save any newly added members to the repository. The following screenshot shows the members' feature:

When you add a new user, Rational Team Concert will automatically ask whether or not you'd like to send a project invitation. This contains all the information the user needs to join the project and start working, including the team repository name, the user ID, and the project area name, as shown next: