Many enterprises still struggle with the decades-old problem of managing a product portfolio consisting of multiple projects and available resources. Transitioning from a traditional waterfall approach to an agile delivery system can be daunting, with challenges such as identifying, prioritizing, and organizing different products potentially costing heavily.
For enterprises following the orthodox model, integration challenges can range from data loss, lengthy timelines, and productivity loss to lack of clarity, among other issues. What is vital for enterprises today is a modern planning solution that is flexible, scalable, and capable of meeting market demands and customer needs.
Digital.ai Agility drives consistency and efficiency by scaling agile practices across all levels, from teams to the entire product portfolio. OpsHub Integration Manager integrates Digital.ai Agility with 60+ best-of-breed industry systems, enabling multi-tool integrations so product and portfolio teams can achieve greater transparency, feasibility, and cross-functional collaboration. This is accomplished in a heterogeneous environment with access to all historical and current data in their preferred systems in real time.
In this video, we will showcase the integration of Digital.ai Agility with Azure DevOps (VSTS/ TFS) using OIM. No portfolio item has been created yet in Azure DevOps (ADO) and Digital.ai Agility. The product manager in Agility creates a portfolio item, gives it a title, selects the type, adds a description and priority, and saves it. Once the portfolio item is created, the product manager adds an attachment under it and saves it. The portfolio item created in Agility synchronizes to ADO as a feature, providing the developer visibility into the feature they need to work on.
In ADO, the developer refreshes the page to view the feature, which has successfully synchronized from Agility. All details, including the remote link, remote ID, and attachment, have successfully synchronized. The developer starts planning the feature by adding a comment as a clarification question to the product team in Agility and changes the state to “Active”, which synchronizes back to Agility as “In Progress”. This automatic bidirectional synchronization enables the product manager and developer to collaborate effectively on feature clarification.
In Agility, the product manager views the updated details under the portfolio item, which were added under the feature in ADO. The product manager adds a reply in the form of a comment and saves it. In ADO, the developer views the comment added by the product manager in Agility. The developer in ADO then starts breaking down the feature into user stories. For the first user story, the developer changes the link type to “Child,” adds a title and description, and saves it. The developer similarly adds a second user story, adds the title and description, and saves it. Both user stories are created and reflected in ADO.
In Agility, the product manager refreshes the page to view the synchronized user stories from ADO. Both user stories are visible and linked to the portfolio item. In ADO, the QA engineer starts adding test cases under each user story. For the first user story, the QA engineer selects the link type as “Tested By,” changes the work item type to “Test Case,” adds a summary, and saves it. The QA engineer then adds another test case under the second user story.
In ADO, the entire hierarchy, including the parent feature, child user stories, and test cases under each user story, is visible. In Agility, the product manager refreshes the page to view the recently added test cases under the first user story, which have synchronized from ADO. The product manager adds a comment and saves it. The product manager then clicks on the second user story, views the test case added under it, and adds a similar comment before saving it.
In ADO, the QA engineer refreshes the page to view the comment added under the test case for the first user story. The QA engineer responds to the product manager’s comment and saves it. Navigating to the test case under the second user story, the QA engineer views the comment synchronized from Agility, adds a reply, and saves it. In Agility, the product manager navigates to the test cases under each user story to view the comments added by the QA engineer in ADO. Both comments have automatically synchronized back to Agility.
The developer in ADO begins working on the user stories, changes their state to Active, and saves them. In Agility, the product manager views the updated status. Back in ADO, the developer changes the state of the user stories to Resolved, and this change in status is reflected in Agility. The QA engineer then changes the state of the test cases first to “Ready”, and then to “Closed, indicating completion.
The QA engineer changes the state of both user stories to “Closed”, indicating the task’s completion. Once the expected results are fulfilled, the product manager in Agility views the updated status. Status changes made to the test cases are also reflected here. All changes made to the status of user stories and test cases in ADO have bidirectionally synchronized to Agility.
Finally, in ADO, the developer changes the state of the feature from “Active” to “Closed”, indicating its completion. In Agility, the product manager navigates to the portfolio item to view the updated status as Closed. This completes the demo.
Thanks for watching. Integrating Digital.ai Agility with other tools using OIM helps teams gain enhanced visibility into the complete delivery ecosystem, enabling them to produce better quality products faster.