Integrate Clarity with Rally
If your organization is using
Clarityto manage investments and their associated funding, and
Rallyfor Agile development and execution, the
Rallyintegration helps bridge the informational gap between investment planning and execution. Oftentimes, reports are used to aggregate data from multiple systems, or spreadsheets, to correlate information related to investment planning and execution status. With this integration, you can,
- Align aRallyinitiative with aClarityproject.
- Associate multipleRallyinvestments and initiatives with a singleClarityproject.
- Fund and track execution across multipleRallyteams.
- Get work details such as features and user stories, fromRallytoClarity.
- Synchronize data bi-directionally to monitor execution activities in eitherClarityorRally.
- Track actuals withinClarityagainstRallyfeatures and user stories.
Rallyintegration, you will obtain the following benefits:
- Transparency: At the project or investment-level inClarity, you have visibility of (but not limited to) execution status, completed work, remaining effort. You will also be able to have an understanding of how the teams’ efforts are aligned with the organizational goals.
- Efficiency: Once you have transparency across your organization, you can streamline the work and reduce waste by building the right things at the right time. You can optimize the flow of value, improve quality, align resources to business priorities, and drive continuous improvement.
- Scope management: With the visibility into the project execution details, you are able to better manage the scope of projects. Based on data, you can decide whether you want to adjust the scope to meet the timelines.
- Delivery Tracking: You can now assess whether a project will complete on time or is at risk of spillover. For example, if a project’s GA date is in a week and there is one month’s worth of work pending, it is unlikely to release on time. You can then decide to either move the delivery timeline or reduce the scope to meet the date.
Consider a simple scenario. A product development organization uses
Clarityfor funding and monitoring investments, and
Rallyfor Agile development and execution. The organization wants to integrate these two systems to gain visibility into investment execution and delivery information. After the integration is configured, data between
Rallyflows as follows:
- Business units define aClarityProject for each initiative that they plan to fund.
- Once the funding for the given project is approved, the Project Manager associates the project with theRallyintegration process. The integration is not automatically enabled for allClarityprojects.
- The Project Manager triggers the synchronization job inClarityto create a corresponding initiative inRally.
- The Project Manager then notifies the Product Manager about the new initiative inRally.
- The Product Manager creates features under the initiative and assigns teams inRally.The integration can also be configured for bidirectional synchronization. This allows teams to create features in either system and synchronize work items across the two systems.
- When the synchronization job runs next time (either scheduled or manually triggered), features and user stories under theRallyinitiative are brought over toClarityas tasks:
- The execution status at the feature-level is also synchronized, providing visibility into the initiative status as shown in the illustration below: