How to manage and customize the process template for your lifecycle project

Process is the collection of roles, practices, rules, and guidelines that are used to organize and control the flow of work. The project process is defined in a project area and can be further customized in a team area. In Jazz, you use process to define user roles and their permissions for performing operations within the tool, such as changing the state of a work item. Each component in Jazz is process aware. In the change and configuration management and quality management project areas, you can add rules of process behavior in the form of preconditions and follow-up actions for these operations. Process can also define project reports, queries, and work item types.

Process Templates provide a starting point and guide for a project area process configuration and iteration structure. They can include process documentation that is in HTML format. You apply a process template when you create a project area. The process can then be modified in the project area or its team areas, independent of the template.

You can create templates from scratch or from existing project areas. Templates are specified in XML by using a schema that can be extended by configuration point declarations. You can edit templates by using source and high-level editors.

Rational Team Concert (RTC) includes a set of templates for common processes, such as Scrum and OpenUp. These templates have been externalized to support translation of text strings into numerous languages. When you create a project area and choose to deploy one of these templates, you can select the language. You can also externalize a process template that you create to support translated versions. Templates for additional processes can be downloaded from jazz.net.

This article assumes that you have installed CLM 4.0.5 and have deployed the process templates in the CLM applications. Please follow the directions in the online help to run setup and deploy templates before continuing. This article also assumes that you know the basic concepts of the project area, team area, process description and practice in the CLM web UI. One of the Process Template already imported into RTC is “Formal Project Management Process-New”.

The Lifecycle Project Administration application includes predefined templates that can use to create a lifecycle project and the project areas that belong to that lifecycle project. The predefined templates define which application project areas to create and which associations are established between those project areas.

The Lifecycle Project Administration application includes the following predefined lifecycle project templates.

Quality Professional, Analyst, Developer

This template sets up associated project areas for quality management, requirements management, and change and configuration management. The testers (in quality management) and analysts (in requirements management) work with developers (in change and configuration management). Quality management tasks and requirements change requests are tracked in the change and configuration management project area. The change and configuration management project area can be configured to use the Scrum, OpenUP, or Formal Project Management process template. The requirements management project area can be configured to use the Requirements Template for Testers, Use Case, Agile Requirements, or Traditional Requirements project template.

There are very few changes that need to be done after you open the XML Document (rational.alm.integrated.template). Change the identifier of the template (for example: from rational.alm.integrated.template to rational.alm.integrated.template_New) and if required also change the title of the document from Quality Professional, Analyst, Developer to Quality Professional, Analyst, Developer-New.

Finally the Lifecycle Project template is ready for import. Click on Import Template as shown below.