Clarity
and Rally Integration Examples

ccppmop1591
To integrate
Clarity
projects with Rally investments, as an administrator, you are responsible for creating the portfolio hierarchy data in
Classic PPM
. See
Define the Portfolio Item Hierarchy
in Integrate
Clarity
with Rally
for details.
The portfolio item hierarchy for Rally investments allows you the flexibility to arrange your items as follows:
  • Skip levels in the portfolio items hierarchy
  • Use more than two levels of items in the portfolio hierarchy
  • Move items around in the portfolio hierarchy
Depending on which portfolio item types you select to synchronize with PPM, the Synchronize job builds the tasks WBS with parent and child tasks in
Classic PPM
. The WBS hierarchy is based on the portfolio item type hierarchy levels or ordinals that you define in Rally. If a direct parent is skipped from the portfolio item hierarchy, the synchronization assumes its next parent as the direct parent. For example, if your portfolio item hierarchy includes only epics and features and skips the initiative level, then the job creates the feature tasks directly under the epic tasks.
When a parent
Clarity
task has actuals, assignments, or both, the integration cannot add a child task under this parent. Instead, the integration adds the child task without a parent. The behavior complies with the rule that summary tasks in
Clarity
cannot have actuals or assignments. The situation applies when synchronizing user stories or portfolio hierarchy items from Rally to
Clarity
tasks.
2
2
Example 1: Simple WBS Synchronized with Rally Investment
The following images show how the Synchronize Agile Central job brings in the portfolio item hierarchy from the relevant Rally investment into the
Clarity
project as tasks:
AC_PIH.PNG
PPM_WBS.png
Example 2: Feature Added to Portfolio Item Hierarchy
For a given investment type integration in PPM,
New Theme
,
Epic
, and
Initiative
are selected for synchronizing. The
Create and Sync Stories
option is selected.
  • In Rally, none of the features associated with the investments have new themes selected.
  • One feature has an associated epic and many features are associated to initiatives.
When the Synchronize job runs, epic, initiative, and user story tasks are created in
Clarity
and existing user stories appear under initiatives as shown in the following image.
PIH_1.jpg
Before the next synchronization, you also select
Feature
in the portfolio item hierarchy for bringing over to PPM. All other configurations remain the same in
Clarity
and Rally.
When the job runs again, feature tasks are now created in PPM. The epic, initiative, and user story tasks remain. The user stories are now moved under features as shown in the following image.
PIH_2.jpg
Example 3: Compare Portfolio Item and Investment Integrations
Available in 15.5.1 and higher, the following image summarizes the difference between portfolio item and investment synchronization. The behavior varies slightly based on whether the synchronization is initated by job or by the action menu command.
lunce-ac-compare.jpg
Examples for Populating Task Dates in
Classic PPM
The following examples describe how task dates in
Classic PPM
are populated based on actual or planned dates of the portfolio items in
Rally
.
3
3
Example 1
:
In this example, the
Classic PPM
task start date is May 15, 2015 and the finish date is June 28,2015 based on the
Rally
actual start and end dates:
Start Date
End or Finish Date
Rally
Actual Start and End Date
May 15, 2015
June 28, 2015
Rally
Planned Start and End Date
May 10, 2015
June 25, 2015
Classic PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015
Example 2:
In this example, the
Classic PPM
task start date is May 15, 2015 based on the
Rally
actual start date. However, the task finish date is June 25, 2015 based on the
Rally
planned end date because the actual end date is not defined.
Start Date
End or Finish Date
Rally
Actual Start and End Date
May 15, 2015
Null
Rally
Planned Start and End Date
May 10, 2015
June 25, 2015
Classic PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015
Example 3:
In this example, the
Classic PPM
task start date is May 15, 2015 based on the
Rally
actual start date. The task finish date is August 5, 2015 based on the project finish date because the
Rally
actual and planned end dates are not defined.
Start Date
End or Finish Date
Rally
Actual Start and End Date
May 15, 2015
Null
Rally
Planned Start and End Date
May 10, 2015
Null
Classic PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015
Example 4:
In this example, the
Classic PPM
task start date is March 20, 2015 and the finish date is August 5, 2015. The task dates are based on the project start and finish dates because the
Rally
actual start date is later than the
Classic PPM
project finish date.
Start Date
End or Finish Date
Rally
Actual Start and End Date
October 15, 2015
Null
Rally
Planned Start and End Date
May 10, 2015
Null
Classic PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015
Example 5:
In this example, the
Classic PPM
task start date is March 20, 2015 based on the project start date. The task finish date is June 28, 2015 based on the
Rally
actual end date.
Start Date
End or Finish Date
Rally
Actual Start and End Date
Null
June 28, 2015
Rally
Planned Start and End Date
Null
June 25, 2015
Classic PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015
Example 6:
In this example, the
Classic PPM
task start date is May 10, 2015 based on the
Rally
planned start date. The task finish date is June 28, 2015 based on the
Rally
actual end date.
Start Date
End or Finish Date
Rally
Actual Start and End Date
Null
June 28, 2015
Rally
Planned Start and End Date
May 10, 2015
June 25, 2015
Classic PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015