DATASHEET

SwiftALM Integration for Azure DevOps Server (TFS) The integration of SwiftALM and Azure DevOps Server (TFS) helps the product management and development teams align their goals and tasks with each other. With integration of these two systems, enterprises can have cross-functional transparency and enriched collaboration across the business and technical verticals.

Integration overview

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 brings in collective wisdom to take better decisions, faster. Best-of-breed systems such as SwiftALM and Azure DevOps Server (TFS) bring rich functionalities to the ecosystem. By integrating SwiftALM with Azure DevOps Server (TFS), enterprises can seamlessly manage the product development.

How SwiftALM - Azure DevOps Server (TFS) With SwiftALM + Azure DevOps Server (TFS) integration, enterprises can: integration is beneficial for an enterprise Make better and faster decisions Trace the requirement breakdown and associated test cases Accelerate time of delivery Get complete context of the business requirement and Ensure complete traceability of a receive real-time updates when there is a change in the plan ‘requirement’ Coordinate on the delivery timelines seamlessly with Get complete view into customer goals concurrent updates on changes and priorities Full traceability into the Quality Assurance (QA) reports Leverage the best of functionality and collaboration in the delivery ecosystem How OpsHub Integration Manager integrates SwiftALM and Azure DevOps Server (TFS)

OpsHub Integration Manager integrates SwiftALM and Azure DevOps Server (TFS) bidirectionally. 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/user stories’ from SwiftALM synchronize to Azure DevOps Server (TFS) and are further broken down to user stories/tasks. When these user stories/tasks are completed in Azure DevOps Server (TFS), the associated requirement/user story in both systems gets updated as well.

User Story Commonly synchronized entities between Requirement SwiftALM and Azure DevOps Server (TFS) (User Story) + Defects The popularly synchronized entities are listed on the left:

OpsHub Inc. www.opshub.com | Call: +1 650 701 1800 Benefits of integration for SwiftALM and Azure DevOps Server (TFS) users

SwiftALM users Azure DevOps Server (TFS) users

Traceability for business requirements throughout Real-time updates on stories and associated the ALM tool chain changes/enhancements

Visibility into the progress of development work & the Complete context of the customer requirements and QA cycle priorities

No dependency on manual communication for No manual efforts needed to keep product making business decisions management teams updated on the development status

Features of OpsHub Integration Manager

Unidirectional as well as bi-directional Full history and audit trail for integrated synchronization systems

Complete traceability of work items as well Robust failure management and recovery as non-work items mechanism

Pre-requisites to run OpsHub Integration Manager

Supported Operating Systems Database Prerequisites

Windows The underlying database should be installed to Windows Server 2012 R2 install and run OpsHub Integration Manager. The Windows Server 2012 database user created for OpsHub Integration Windows Server 2008 R2 (64 bit) Manager should have schema level and read write Linux privileges.

RHEL 5.2 + (64 bit) RHEL includes Cent OS and Fedora MySQL Server MS SQL Tested on the following versions: Oracle CentOS release 5.5 (Final) HSQLDB CentOS release 5.6 (Final) CentOS Linux release 7.1.1503 (Core) Fedora 20

OpsHub Inc. www.opshub.com | Call: +1 650 701 1800