When it comes to effective portfolio management of multiple projects between cross-functional teams, having enterprise-grade integration support is crucial to deliver high-quality products faster. Product managers need quick visibility into development progress. Similarly, developers need clarity on customer expectations and business requirements. Today, we will show how integrating Digital.ai Agility, Jira, and OpenText ALM (Formerly known as Micro Focus ALM, HP ALM) used by the product owner, developer, and QA team, creates a seamless communication chain across the product lifecycle.
Digital.ai Agility is a powerful agile planning solution that drives consistency and efficiency by scaling agile practices across all levels, from teams to the entire product portfolio, while Jira is an issue or work execution tool that enables bug tracking and agile development. Let’s see how OpsHub Integration Manager (OIM) enables the integration between Digital.ai Agility, Jira, and OpenText ALM and offers product managers, developers, and QA teams cross-functional data in their preferred system.
The product team in Agility adds a new portfolio item, gives it a title, description, and priority, and saves it. In Jira, the development team views the recently synced portfolio item from Agility as a feature. All details attached to the portfolio item, including the title, description, remote ID, remote link, and priority added in Agility, are also reflected here under the feature. The development team in Jira now starts planning for the feature, adds a comment as a clarification, and attaches a file, which will get bidirectionally synced back to Agility.
This will help the product and development teams collaborate effectively for feature clarification. Back in Agility, the product team clicks on the portfolio item to view the attachment, remote ID, remote link, and comment from Jira, and as a reply to the development team, adds a comment. In Jira, the development team refreshes the page to view the recently added comment, which has synced back from Agility. The development team now goes ahead and changes the status of the feature to In Progress and breaks the feature into user stories. Under the user story, the development team adds a title, description, and a parent-child relationship.
The user story created in Jira will also get synchronized to OpenText ALM as a requirement, giving the QA team visibility for testing. We can see that the user story has been created back in Agility. The product team refreshes the page to view the user story, which has automatically synced from Jira, along with the status of the portfolio item, which is also reflecting In Progress. Under the user story, the product team views the recently synced title, description, remote ID, and remote link. Navigating to OpenText ALM, the QA team views the user story and begins creating test cases.
These test cases will synchronize to Agility and Jira with their relation to stories. This way, the product and development teams will get complete clarity on the testing strategy for a given user story. Under the test case, the QA team adds a name and description and changes the status to New. The QA team now links the test case to the same user story. Back in Jira, the development team views the test case, which has synced back from OpenText ALM. The same test case created in icr OpenText ALM is also reflected in Agility.
We can see all details associated with the test case also synced back. The product team in Agility now adds a comment as a suggestion for the testing strategy and saves it. This will get synchronized to Jira and OpenText ALM. In OpenText ALM, the QA team views the comment from Agility and refines the test accordingly. Once done, the QA team adds a comment as a reply, notifying the product team of the same. Back in Agility, the product team refreshes the page to view the comment added in OpenText ALM.
We saw how the product team in Agility and the QA team in OpenText ALM collaborated effectively to work around the issue while providing the development team in Jira with complete visibility into the latest activities at all times. Here in Jira, we can see both the comments from Agility and OpenText ALM synced successfully. The development team in Jira now goes ahead and changes the status of the user story to Done, marking the completion of the same. In OpenText ALM, the QA team views the updated status of the requirement to “Complete” and changes the status of the test case from New to Passed.
In Jira, the development team views the updated status of the test case, which is reflecting Done, and then changes the status of the feature from “In Progress” to “Done”. Finally, navigating to Agility, the product team refreshes the page to view the recently synchronized status of the feature, user story, and test case. Here, we can see the status of the user story showing “Resolved”, the status of the test case indicating “Passed”, and the status of the feature reflecting “Closed”.
This completes the demo. Thank you for watching.
OpsHub Integration Manager (OIM) integrates Digital.ai Agility with 60 best-of-breed industry systems.
