In an Application Lifecycle Management (ALM) ecosystem, the choice of systems and the collaboration between the cross-functional teams play a great role. While the choice of systems impacts the productivity of a team, the cross-functional collaboration helps the teams get complete context of the business requirements. Best-of-breed systems such as Micro Focus ALM/QC and RALLY bring rich functionalities to the ecosystem. Integration of Micro Focus ALM/QC with RALLY ensures that the development and QA teams are on the same page when it comes to delivery timelines and have complete visibility into each other’s tasks.
Download PDF 
Micro Focus ALM/QC CA Agile Central Integration Overview
The integration of Micro Focus ALM/QC and RALLY helps in bringing the product development and Quality Assurance (QA) team on the same page. As both the teams have visibility into each other’s task and complete context of customer expectations, the quality of product is better, and the delivery cycle is shorter.
Best-of-breed systems such as Micro Focus ALM/QC and RALLY bring rich functionalities to the ecosystem. Integration of Micro Focus ALM/QC with RALLY ensures that the development and QA teams are on the same page when it comes to delivery timelines and have complete visibility into each other’s tasks.
How Micro Focus ALM/QC – CA Agile Central integration is beneficial for an enterprise
- Access to QA plans and defects in real time
- Real-time updates on the status of a story, its estimated time of delivery, and any risks that might delay the impending release
- Complete context of the customer requirement and visibility into codes written by the development team & test cases
written by QA team - Coordinate on the delivery timelines seamlessly with concurrent updates on changes
With Micro Focus ALM/QC + CA Agile Central (RALLY) integration, enterprises can:
How OpsHub Integration Manager integrates Micro Focus ALM/QC and RALLY
OpsHub Integration Manager integrates Micro Focus ALM/QC and RALLY in a bidirectional manner. It ensures that all historical and current data is available to each user, in that user’s preferred system, with full context, in real-time. All ‘requirements’ from RALLY automatically synchronize to Micro Focus ALM/QC where they are broken down to ‘stories’. The completion of the story and the status of test results against it automatically synchronizes to RALLY.
Popularly synchronized entities
Use Case: Micro Focus ALM/QC Integration with CA Agile Central (Rally)
Problem statement: The development team creates sprints, and requirements in RALLY – which is the development system and replicate the same in Micro Focus ALM/QC – which is used by the QA team. The defects are created in Micro Focus ALM/QC and then replicated in RALLY. Manual replication of data takes a lot of time and effort.
Solution: When RALLY and Micro Focus ALM/QC are integrated, there will not be any duplication of efforts and the data between both the systems will synchronize in real time.
- The development team, then, creates ‘sprint’ in RALLY with basic attributes, which synchronizes to Micro Focus ALM/QC as a ‘cycle’.
- The development team then creates ‘User Story’ in the already created sprint in RALLY. The ‘requirements’ sync to Micro Focus ALM/QC with traceability of cycle and release.
- The developer then works on the ‘User Story’ and updates the status of the ‘User Story’ to ‘Completed’ in RALLY, which again synchronizes to status of the ‘requirement’ in Micro Focus ALM/QC.
- The QA team, then runs a quality test and finds a ‘defect’. They log the defect in Micro Focus ALM/QC, which synchronizes to the ‘User Story’ in RALLY.
Benefits of integration for Micro Focus ALM/QC and CA Agile Central (RALLY) users
Micro Focus ALM/QC users
- Real-time updates on the story and associated changes/enhancements
- Access to the business requirements, development status, and associated updates from within Micro Focus ALM/QC
- Seamless coordination on iteration start and end date
CA Agile Central (RALLY) users
- No duplication of efforts for entering the same data in multiple systems
- Clear visibility into quality parameters, QA schedule, test cases, and test results
- Seamless coordination on iteration start and end date