Configure the Agile Time Tracking Project Template

Use the Time Tracking Project Template available with the Agile add-in to integrate cappm with rally.The template contains the following time tracking tasks that are automatically generated for any new features imported from rally. 
ccppmod152
Use the Time Tracking Project Template available with the Agile add-in to integrate
CA PPM
 with
CA Agile Central
.The template contains the following time tracking tasks that are automatically generated for any new features imported from 
CA Agile Central
  • Design
  • Development
  • Test/QA
  • Documentation
With these high-level tasks in place by default, project teams can focus on defining and capturing the actual work using stories and tasks.
Recommendations for Creating the Project Template 
  • Use the project template included in the Agile add-in as an example when creating additional time tracking project templates. Define only a small number of tasks for the template.
  • The charge code and cost type values are not populated for these tasks by default in the template. Select these values for your tasks in the project template before using the template for the integration.
  • The template supports a hierarchical work breakdown structure. However, If you need to create a hierarchy, keep the levels at a minimum. A hierarchy with a large number of levels can impact performance.
After the integration is set up and the Rally Synchronization job runs for the first time, the following changes are reflected in
CA PPM
:
  • The
    CA Agile Central
    portfolio item is brought in as a new task in
    CA PPM
    , if it is not already there. The new task is created based on the Portfolio Item Type Map (Task) value defined in the integration instance.
  • The tasks from the Agile Time Tracking Project Template are automatically created as sub-tasks under the new task in 
    CA PPM
    .
During subsequent synchronizations, the sub tasks are updated to reflect the latest status from the
CA Agile Central
portfolio item.
Example
An integration instance is setup using the following defaults:
  • CA PPM
    projects are mapped to initiative portfolio items in
    CA Agile Central
  • CA PPM
    tasks are mapped to feature portfolio items in
    CA Agile Central
  • The Create and Sync Tasks option is selected.
The following high-level process describes how you synchronize and update the agile projects:
  1. In
    CA PPM
    , create and associate a time tracking project template to the integration instance.
  2. In 
    CA PPM
    , create a project and connect it to
    CA Agile Central
    .
  3. Run the Rally Synchronization job to create the 
    CA PPM
    project as an initiative in
    CA Agile Central
    .
  4. Create features under the linked initiative in
    CA Agile Central
    . The next time the Rally Synchronization job runs, it creates tasks in 
    CA PPM
    corresponding to these features. At this point, the tasks in the Agile Time Tracking template are automatically created as sub tasks underneath the feature tasks.
As you create new features for the initiative in
CA Agile Central
, the process repeats. New tasks and sub tasks are created automatically in
CA PPM
corresponding to the new features.
Rules for Naming Sub-tasks Created from Templates
The Rally Synchronization job creates the sub-tasks in
CA PPM
based on the following rules:
  • Sub-task name. The sub-task name starts with the portfolio item ID displayed in parentheses, followed by the task name from the Time Tracking Project Template. The sub-task name is truncated if it exceeds 150 characters. The last 5 characters are replaced by '...' indicating that the task name continues. We recommend that you use shorter task names when creating a custom template.
  • Sub-task ID. The sub-task ID starts with the portfolio item ID, followed by the task ID from the Time Tracking Project Template, separated by a dot ("."). The task ID in the template can follow any mask or contain any value including null values. When the synchronization job creates the sub-task, it does not consider the task ID in the template. The sub-task ID is always formatted regardless of what is defined in the template. If the portfolio item ID exceeds 12 characters, then it is modified to contain only the first two characters followed by the task ID number from the template. This is required because task IDs are limited to 16 characters in 
    CA PPM
    . In
    CA Agile Central
    there are no such limits. The task number is a counter limited to 999 tasks, however we do not recommend a template with a large number of tasks as It can impact performance.
For example, the following information is available for an integration instance:
  • Portfolio item: Feature A
  • Portfolio item ID: F123
  • Template task name: Design
  • Template task ID: 001
In this case, the job creates a sub-task with the following name and ID in
CA PPM
:
  • Sub-task name: (F123) Design
  • Sub-task ID: F123.001