1. Log on to a user with Project Area Administrator privileges 

A project area can only be configured by someone with the Project Area Administrator role for that project area.  This role should have been assigned as part of Creating an "Agile ALM with Scrum" Project.

Logging in for project administrators and team leads.

2. Define project timelines

When the project area was created, a default timeline was created.

Update the start and end dates for the first release to be correct for your project.

Add additional Sprints to the timeline as needed for the first release.

Update the start and end dates of each Sprint to match your preferred Sprint duration.

It is good practice to avoid any gaps between start and end of a timeline. If gaps should exist and work items are completed during such a gap, the burndown charts would not be able to catch this and would thus be broken.

By default, there will not be gaps, because iterations will start at 12.00 AM and end at 11.59 PM.

Creating timelines and iterations 

Modifying timelines and iterations.

3. Configure project dashboard

Dashboards contain widgets that provide real-time information. You might want to add, remove, or customize widgets. This is done on regular basis, as different reports and measurements are needed throughout the project.   

Examples of widgets you may remove are the Customize Your Dashboard and Welcome to Rational Team Concert widgets.

Accessing a project or team dashboard

Getting started with dashboards

Managing Dashboards

Working with Widgets

Configuring widgets.

4. Update views for the plans

Projects may refine the content and organization of different plan views. Any changes made to the plan views are automatically applied to those plan views for all plans of the same type.

See below for some recommended view customizations.

4.1 Product Backlog Work Breakdown view

a. Remove Effective Estimate.

The team does not focus on estimates in the Product Backlog. They will rank stories according to their Business Value.

b. Move Rank to be after Summary.

c. Add Business Value and move it after Rank

d. Add Planned for

4.2. Release Backlog Work Breakdown view

Apply the same steps as for the Product Backlog.

4.3 Sprint Backlog Work Breakdown view

a. Move Rank to be after Summary.

b. Add Business Value and move it after Rank

4.4 Sprint Backlog Storyboard view

Change Display > Taskboard to Display > Kanban to enable the status of stories to be updated using drag and drop. 

5. (optional) Define Defect "Found in" Values

Defects have a "Found in" attribute that can be used to categorize the defect by the kind of release in which it was found.
A candidate set of release kinds you could start with are:

• Production
• User Acceptance Test
• Integration Test
• Performance Test
• Development

Defining releases in the web client that work items can be filed against

6. Create team areas

The structure of the project teams is defined by a hierarchy of team areas. Several cross-functional teams can work in the same project area.

Create a team area for each team on the project.  The template provides a default dashboard that will be customized in later steps.

Creating a team area

7. Create categories and assign to team areas

Categories are used to group work items by code area, project component, or area of focus. Since different teams work on different code areas each team must have at least one category. Additional categories are optional.

The Scrum – Agile ALM template comes with two default categories; one Unassigned (ROOT Category) and one sub category with the name of the project area.

Create subcategories of the project area category, one or more categories for each team. Assign each category to the appropriate team.  If you assign a parent category to a team, the child categories are inherited by that team automatically.

Defining categories that work items can be filed against

8. Add Scrum Master to teams 

Configuring the team area must be done by a a member of the team. Identify the person that will be acting as the Scrum Master for each team, and add them to the created team area with the role of Scrum Master.

Other members will be added (and automatically invited to the team), when the team area is configured.

Note that all project team members must be registered users in the Jazz repository.  See Creating users.

Adding and modifying users as members of project areas and team areas.