Jama – Azure DevOps Server (TFS) 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) integration is beneficial for an enterprise
- Trace the requirement breakdown completely – access the features, product backlogs, tasks associated with the requirement
- Track the estimated and actual development efforts
- Get complete context of the business requirement and receive real-time updates when there is a change in the plan
- Coordinate on the delivery timelines seamlessly with concurrent updates on changes
- Get full traceability into the Quality Assurance (QA) reports from both systems
With Jama + Azure DevOps Server (TFS) integration, enterprises can:
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.
Popularly synchronized entities
Use Case: Jama integration with Azure DevOps Server (TFS)
Problem statement: The product management uses Jama and the development team uses Azure DevOps Server (TFS). However, as the systems are not synchronized, any change to customer requirement must be manually communicated to the development team. The product manager also doesn’t have real-time visibility into the development plan and estimated timeline for a given requirement.
Solution: When Jama and Azure DevOps Server (TFS) are integrated using OpsHub Integration Manager, the coordination between the product management team and development team will be seamless.
- The Product Manager creates a ‘business requirement’ in Jama and adds descriptive comments for the development team.
- The ‘business requirement’ synchronizes to Azure DevOps Server (TFS) as a ‘requirement’. The development team breaks it into ‘user stories’ and starts work on it.
- Due to a sudden escalation, the Product Manager changes the priority of this ‘business requirement’ in Jama and marks it as ‘minor’. The Product Manager also adds comment to change the delivery deadline of this requirement.
- The changes synchronize to Azure DevOps Server (TFS).
- The development team updates the delivery date of the ‘requirement’, which synchronizes to Jama.
Benefits of integration for Jama and Azure DevOps Server (TFS) users
- Traceability for business requirements throughout
the ALM tool chain
- Visibility into the progress of development work
- No dependency on manual communication for
making business decisions
Azure DevOps Server (TFS) users
- Access to the business requirements and associated updates from within Azure DevOps Server (TFS)
- Complete context of the customer requirements and priorities
- No manual efforts needed to keep product management teams updated on the development status