Frequentis develops safety-critical solutions for many highly regulated industries. Requirements and their test cases are thus painstakingly authored in a fit-for-purpose tool called Jama Connect. The software developers, who implement the requirements as code, plan and execute their work in Atlassian Jira, a popular work management tool.
Regulatory compliance mandates traceability from requirements to code, meaning the ability to trace a requirement to the code that implements it and to evidence that it has been properly tested. For this purpose, Frequentis had been utilizing a native Jama connector to synchronize data between Jama and Jira and establish Jama as a main source of truth for compliance reporting. All Frequentis software specialists had come to rely on the integration to duplicate data between the tools on their behalf and allow them to stay in their tool of choice.
While useful, the native integration wasn’t perfect: It typically took several hours for data to flow between the systems, slowing teams down as they waited for new requirements or defects to sync over to Jira or for status updates to flow back to their colleagues in Jama. In addition, each project team was responsible for defining the configuration of the integration, which took time away from developing new revenue-generating capabilities.
When Jama announced it would be retiring its native Jira connector, Frequentis seized the opportunity to find a powerful and scalable replacement that would optimize efficiency and productivity in product development.
After a rigorous search (that included several proofs-of-concept and pilots) and with the warm endorsement of Jama, Frequentis decided to purchase Tasktop Hub. Hub is an off-the-shelf integration platform that could take over as the critical bridge between the tools while further optimizing software delivery operations:
Tasktop Hub could maximize individual productivity and reduce communication delays by significantly improving the speed of data exchange.
Tasktop Hub could eliminate the costly overhead of setting up and administering the integrations by creating standardized, reusable integration models.
Tasktop Hub would allow Frequentis to upgrade their Jama and Jira instances freely as new versions become available, without breaking their integrations or metrics.
Business Continuity throughout the Migration Period
With the native connector’s end-of-life date fast approaching, the migration to Tasktop Hub began briskly. The Hub installation and initial configuration went very smoothly, and Sr. IT System Engineer Manuel Scharfy was trained on setting up the initial integration models. Models are reusable configuration elements that standardize the data flow between systems and allow Hub administrators like Manuel to spin up new integrations within minutes.
Manuel prepped over 100 projects for the migration to ensure that existing pairings and links from previously synchronized artifacts would be maintained once Hub took over. In parallel, new integrations were set up directly on Hub, harnessing the preconfigured models. In June 2020, Frequentis began using Hub in production.
In the six months since the migration, Frequentis estimates that Hub’s model-based integration has delivered significant time savings that can now be devoted to product development. The time previously spent on point-to- point field mapping between hundreds of Jama and Jira project pairs was replaced by seven integrations that easily scale to hundreds of projects.
Furthermore, Hub’s excellent and detailed administration UI has made it easy to troubleshoot and correct errors without spending countless hours digging through log files, as they’d previously been forced to do.