I created a Lifecycle project for a customer using the Analyst template because they wanted to evaluate how RRC could import a bunch of requirements from an older Doors database. Well, they liked what they saw and now they would like to create some models and store them using RTC.

After reading the Lifecycle Project Templates section of the documentation, the only difference between the Analyst and Analyst/Developer templates is that Implementation Requests are provided from CCM to RM in the Analyst/Developer template. So I added the 'Provide Implementation Requests' association to the CCM project.

The Lifecycle now appears to be equivalent to a test project that I created using the Analyst/Developer template. Are there any other changes that need to be made? (It couldn't possibly be this easy, right?)

Thanks,
Fran Kemp

I am assuming you are referring to this documentation?

http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.jazz.platform.doc%2Ftopics%2Fc_lifecycle_project_templates.html

The main purpose of LPA templates is to create and manage application project areas and establish associations.

So once the project areas are created you can add other permitted associations, for example adding to the Implementation Requirements association between RM and CCM, an additional association for Requirements Change Requests. Adding associations is quite simple.

Hi Fran,

In terms of the associations between project areas, you are correct that the only difference is that the Analyst, Developer template has both Implementation Requests and Requirements Change Requests associations, while Analyst only has the latter.

There is one other difference which might not matter for your customer: when you create a Lifecycle Project using the Analyst, Developer template, you are allowed to choose between three predefined process templates for the RTC project: Scrum, Open UP, and Formal Process Management Process. With the Analyst template, the only choice for the RTC project's process template is the basic Simple template. If the customer is only interested in the types of artifacts that can be created in RTC, they will probably be content with the simple template. If they are interested in following a prescribed development process with a team and well-defined schedule, they may be interested in one of the richer process templates. A project's process specification can be customized extensively, but the starting process template for a project is locked in place when it's created, and cannot be changed.

To answer your question with confidence, I downloaded the XML for both of the templates on the Templates page in LPA and compared them. If you're familiar with the properties of a project area, the syntax should be mostly self-explanatory, but a detailed reference can be found at: https://jazz.net/wiki/bin/view/Main/LPATemplateSpec.

Hello,

Moving a project area from one process to another is largely a manual process involving editing the project area specification XML. It is non-trivial and varies in difficulty depending on how closely related the template used to create the project area and the process you want to follow are.

Moving from the Simple process to the Scrum process would be a chunk of work for someone very familiar with process configuration. In addition to the different roles and permissions, the Scrum template defines different types of data (such as work items). Moving to Scrum would involve mapping existing artifacts to the new types.

In short, it is non-trivial and I would not recommend it. :>

But, as the project evolves, the team can choose to extend the simple process with more roles, work item types, etc following the usual process management practices.

Martha
Jazz L3 Developer

Hi Fran,

In terms of the associations between project areas, you are correct that the only difference is that the Analyst, Developer template has both Implementation Requests and Requirements Change Requests associations, while Analyst only has the latter.

There is one other difference which might not matter for your customer: when you create a Lifecycle Project using the Analyst, Developer template, you are allowed to choose between three predefined process templates for the RTC project: Scrum, Open UP, and Formal Process Management Process. With the Analyst template, the only choice for the RTC project's process template is the basic Simple template. If the customer is only interested in the types of artifacts that can be created in RTC, they will probably be content with the simple template. If they are interested in following a prescribed development process with a team and well-defined schedule, they may be interested in one of the richer process templates. A project's process specification can be customized extensively, but the starting process template for a project is locked in place when it's created, and cannot be changed.

To answer your question with confidence, I downloaded the XML for both of the templates on the Templates page in LPA and compared them. If you're familiar with the properties of a project area, the syntax should be mostly self-explanatory, but a detailed reference can be found at: https://jazz.net/wiki/bin/view/Main/LPATemplateSpec.

David, that's exactly what I was looking for. I think they will be happy with the Simple process. If they are not, how difficult is it to upgrade to the scrum process? I know it is a manual job, but I think learning it will be useful in the future.



Thanks,
Fran