< Previous | Next >

Lesson 1: Add support for multiple timelines and team areas

You can associate artifacts, such as timelines, test plans, and test cases, to team areas if you enable support for timelines and team areas in your project. When that support is enabled, your team can fully govern the project area so that the behavior of the application can differ between users, teams, or points in time.

Before you begin

Before you begin, make sure that you have JazzAdmins repository permissions and these client access licenses:
  • Rational Quality Manager - Quality Professional
  • Rational Team Concert - Developer

About this task

In a project area, you can create one or more timelines that define how a period is partitioned into a hierarchy of iterations. With team areas, you can subdivide your project areas into smaller teams and assign varying permissions to different roles on each team.

By default in the Quality Management application, only one timeline per project area can be used, and team areas are not supported. However, you can enable the use of multiple timelines and team areas in the project properties. Then, you can create more timelines and assign them to either the project area or any team areas that you create.

In this lesson, the JKE Banking team decided that they can better support agile development and continuous delivery processes by creating a run team that focuses on defects and enhancements for current releases. The JKE Banking test team wants the run team to use the JKE Testing team area, and to be associated with a new timeline named "Maintenance." First, the project administrator must activate support for multiple timelines and team areas.

For a demonstration of how to enable and use multiple timelines and team areas in the quality management application, watch this video:
Video about enabling and using team areas

Enable support for timelines and team areas

Procedure

  1. Log on to the JKE Banking (Quality Management) project dashboard at https://fully-qualified-host-name:9443/qm/web/console/JKE Banking (Quality Management) as a user who has JazzAdmins repository permissions and the required client access licenses.

    Throughout this tutorial, this user is referred to as Bert.

  2. In the upper-right portion of the Quality Management application, click the Administration Administration icon, and then click Manage Project Properties.
  3. From the list of properties on the left, click Team Areas and Timelines.
    The graphic shows the Team Areas and Timelines page of the Project Properties.
  4. Select the Enable team areas and support for multiple timelines check box.
  5. Click Save.

Create a maintenance timeline and iterations

During release planning, the team determined a schedule for the upcoming maintenance release. Now, Bert creates the timeline and iterations that are associated with the next release of the JKE Banking application.

About this task

In the Customize process in your project area and team areas tutorial, Bert created the Maintenance timeline in the Customization Tutorial Project (Change Management) project area. Complete these same steps to create another maintenance timeline in the JKE Banking (Quality Management) project area.

Procedure

  1. In the upper-right portion of the Quality Management application banner, click the Administration Administration icon, and then click Manage This Project Area > Timelines. The Scrum process, which the project area is based on, defines one timeline, Main Development. Development teams typically use the Main Development timeline to track their main releases, such as Version 1.0 and Version 2.0. To track maintenance releases, it is common to use a separate timeline.
  2. Go to Lesson 2: Create a timeline and iterations and complete steps 2 - 4.
  3. Select the new Sprint 1 iteration; then, click Edit Properties. Notice that by default, the A release is scheduled for this iteration check box is selected. In order for a test plan to use the iteration, this setting must be enabled. Although you can create a schedule that is based on a single iteration milestone, typically the schedule is created from the parent iteration to include all child iterations. In this example, Release 1.0.1 is the parent iteration.
    The screen capture shows the Edit the Iteration window.

Edit a team area for the run team

Repurpose a team area in the JKE Banking project, JKE Testing, so that the new run team can use it.

Procedure

  1. In the project area, click Overview.
  2. In the Team Area Hierarchy section, click JKE Testing. Bert knows that the JKE Testing team area was originally conceived as the team area for Release 2 of JKE Banking. Because the test team is now divided into a feature team and a run team, the JKE Testing team area can be updated.
  3. At the top, edit the team area name by selecting Testing and typing Run Team.
  4. In the Details section, click Edit.
  5. In the Summary field, select Testing and change the name by typing Run Team.
  6. In Description, select Release 2 and edit the text by typing maintenance releases. The team area Overview looks like this example:
    The graphic shows the Overview section with the text edits.
  7. By default, team areas are associated to the project timeline. When team areas and multiple timelines can be created in a project, separate teams can work in tandem on independent schedules. To associate the team area with the new timeline, under Timeline, select Maintenance.
  8. Click Save.

Lesson checkpoint

In this lesson, you learned how to do these tasks:
  • Enable support for multiple timelines and team areas
  • Create a timeline
  • Edit a team area and associate it with a non-project timeline
< Previous | Next >

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki