Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Global Configuration for every release - Concept and Problems

Questions
Tags
Users
Badges
Jagadeesh Jayapal
(28●4) edited
Feb 04 '19, 9:44 a.m.

(Sorry for the long post. It cannot be said short.)

Background - Our team is working on the concept of JAZZ global baseline for releases – GC creation for every release.

The steps are explained below:

STEP 1: Define requirements – Baseline DNG – Create release GC and add this baseline.
 The requirements are defined in DNG in the context of project Development GC eg: GC – AB_Development. Traceability links within the requirements are established. Those requirements that are completed becomes part of a release. A release baseline eg: BL_DNG_AB1910 is created in DNG there by also creating a release GC eg:  GC – AB1910 and attaching the baseline.

STEP 2: Implement requirements – Create RTC Iteration and stories for the baselined requirements. Associate release gc to the iteration.

While the requirements are being defined in DNG, project RTC admin starts creating release iterations eg: RTC_AB190 in the RTC timeline and associates the development GC to the iteration in the RTC releases section (This activity take place even before the requirements are complete). The project manager starts creating the RTC stories from requirements and assigns to the project backlog iteration. The backlog iteration is associated to the development GC. After the requirements are frozen and a releases GC has been created as described in the step 1 above the corresponding RTC work items are moved from the backlog iteration to the release iteration !.  Also the development GC is replaced by the release GC in the RTC releases section for this iteration. 

STEP 3: Integration and Verification – Complete verification activity, baseline RQM and replace the RQM stream in the release GC.

The integration and verification activities are carried out on the baselined requirements for release GC – AB1910. The testcases are linked to the requirements using this GC. Once the verification activities are completed a baseline is created eg: BL_RQM_AB1910. This baseline replaces the RQM stream in the release gc.

Problem: From Step 2:  RTC work items are moved from the backlog iteration to the release iteration

As the RTC work items are moved from the backlog iteration (which was associated to the development GC – AB_Development) to the release GC – AB1910 the traceability links also moves to the release gc leading to the following situation:

A full view of the RTC In progress/ implemented work items from the development eg:  GC – AB_Development  is not posible. The RTC work items are distribute to several release GCs. So a consolidated report of the project status from a single GC is not possible. Is it possible to get a full view of RTC work item status from a single gc (Ideal is from development as the traceability links were first established) instead of several release gcs?. 

Please help to review our concept and guide us out of this situation.

<o:p> </o:p>

<o:p> </o:p>

0 votes

1 answer
2,363 views
0 votes

One answer

Permanent link
Stefan Oblinger
(185●2●13) edited
Mar 29 '19, 2:52 a.m.
There are several questions concerning your concept:

STEP 1:

Are "GC – AB1910" and "GC – AB_Development" different Global Components?
Or these the names of two streams within the same Global Component where the "GC – AB_Development" stream is derived from "GC – AB1910" stream?

STEP 2:

Why are you associating Release Iteration RTC_AB190 to the Development GC?

Are there any Work Items associated to Release Iteration RTC_AB190 before the Work Items are moved from Backlog to Release Iteration?

Do the developers actively work on the Work Items while they are associated to the Backlog Iteration?
If not, then exists no reason to associate the Backlog Iteration to any GC.
If yes, then you seem to (mis-)use the Backlog Iteration as a Development Iteration.
Please explain following statement:

As the RTC work items are moved from the backlog iteration (which was associated to the development GC – AB_Development) to the release GC – AB1910 the traceability links also moves to the release gc ...


  1. Which tracability links?
  2. Who moves the tracability links?

A full view of the RTC In progress/ implemented work items from the development eg:  GC – AB_Development  is not posible.

Why not? You can create a work item query to select all the work items that are planned for the iterations that belong to the GC. Or are you talking about a JRS report?

In addition to the solution please also describe the intention therefore.

Stefan

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,495
× 239

Question asked: Feb 04 '19, 9:00 a.m.

Question was seen: 2,363 times

Last updated: Mar 29 '19, 2:52 a.m.

Confirmation Cancel Confirm