Introduction
This guideline describes how to take a delivery process from IBM® Rational® Method Composer and create a matching IBM®
Rational Team Concert™ process template.
Among the benefits of this mapping is that the breakdown structure (tasks and activities) documented in the process are
mirrored as work items in a matching Rational Team Concert process template. This saves time creating work items,
ensures consistency with the process, and helps team members find the guidance that they need to do their work.
This guideline is based on work creating a process template that matches the IBM Practices for Agile Delivery process.
This paper proposes general rules that can be applied to any delivery process.
Work Breakdown Structure - Mapping Rules
A typical work breakdown structure (WBS) can include lifecycle phases such Inception, Elaboration, Construction, and
Transition. Each phase can contain one or more iterations (also called time-boxes) where increments of work are
created. Each iteration can be made of sub-phases (in the example in Figure 1, the sub-phases are Plan, Execute, and
Stabilize), and each sub-phase can contain activities, sub-activities, and tasks.
Sub-phases are an optional level of organization in the iteration WBS. Alternatively, the activities and tasks can be
added directly under the iteration element without the use of sub-phases.
The following are generic mapping rules that describe how typical elements in a WBS map to elements in Rational Team
Concert process template.
Rule 1: WBS phases and iterations should map to the timeline that is automatically populated as part
of creating a new project in Rational Team Concert. Make sure that the process template contains the phases and
iterations in the timeline by editing the process template description.
Rule 2: Sub-phases are an optional level of organization that can be added to the WBS. Sub-phases
should be represented in Rational Team Concert in one of two ways:
-
As folders
-
As tasks in the iteration plan.
Either way, the planned tasks are nested under the sub-phases in the iteration plan.
Rule 3: Planned activities and tasks should map to tasks in Rational Team Concert, observing the
hierarchy (nesting) found in the WBS
Rule 4: Multiple occurrences of the Develop User Story activity should be represented in one of
two ways:
-
As a flat list of many work items of the Story type per iteration, where the story name follows this
convention: Develop User Story: <story name>.
-
One occurrence of the Develop User Story task per iteration, with many work items of the Story type added
as child items of this task.
Rule 5: Multiple occurrences of the Fix Defect activity should be represented in one of two
ways:
-
As a flat list of many work items of the Defect type per iteration, where the defect name follows this
convention: Fix Defect: <defect short description>
-
One occurrence of the Fix Defect task per iteration, with many work items of Defect type added as child
items of this task.
|