DATASHEET

Jama Integration with Azure DevOps Server (TFS)

The integration of Jama with Azure DevOps Server (TFS) brings the business and product development teams together to accelerate product develop- ment and efficiently scale agile practices.

Integration overview

In an Application Lifecycle Management (ALM) environment, the choice of systems and the collaboration between the cross-functional teams play a great role in delivering quality solutions. 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 Jama and Azure DevOps Server (TFS) bring rich functionalities to the ecosystem. By integrating Jama with Azure DevOps Server (TFS), enterprises can diminish the collaboration barriers between product and development teams that otherwise lead to quality issues, delivery delays, and financial loss.

How Jama - Azure DevOps Server (TFS) With Jama + Azure DevOps Server integration is beneficial for an enterprise (TFS) integration, enterprises can: Trace the requirement breakdown completely - access Make better and faster decisions the features, product backlogs, tasks associated with the requirement Enhance collaboration between business Track the estimated and actual development efforts and backend teams Ensure complete traceability of Get complete context of the business requirement and receive real-time updates when there is a change in the plan a ‘requirement’ Get complete context of business goals Coordinate on the delivery timelines seamlessly with concurrent updates on changes and priorities Get full traceability into the Quality Assurance (QA) reports Leverage the best of functionality and from both systems collaboration in the delivery ecosystem

How OpsHub Integration Manager integrates Jama and Azure DevOps Server (TFS)

OpsHub Integration Manager integrates Jama 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’ from Jama automatically synchronize to Azure DevOps Server (TFS) and all the entities and details associated with the ‘requirement’ synchronize back to Jama.

Feature Feature

Requirement Requirement Entities that can be synchronized

User Story Task between Jama and Azure DevOps Server (TFS) + The popularly synchronized ones are listed on Defect Bug the left: Test Case Test Case

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

Jama users Azure DevOps Server (TFS) users

Traceability for business requirements throughout Access to the business requirements and associated the ALM tool chain updates from within Azure DevOps Server (TFS)

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

No dependency on manual communication for No manual efforts needed to keep product management making business decisions 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 Robust failure management and recovery well 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