Common Integration Patterns in Enterprise Software Delivery

Posted by

At Tasktop, we’ve taken measures to better understand the usage of the Tasktop Integration Hub to learn more about how companies are currently using our product, and how we can continue to enhance it to meet the ever-changing needs of our discerning customers.

Recently, we studied over 300 software architecture and value stream customer diagrams to create metrics around how different companies currently use, or would like to use, our product.

These diagrams contained information around the tools, artifacts, and integration patterns that made up each company’s software architecture and value stream. We unearthed a well of knowledge that ended up providing more than great metrics; we gained a deeper understanding of the complexity of our customers’ businesses and their integration use cases.

We have uncovered a set of common integration patterns between teams and their tools that we have optimized based on our broad experience with integrating the software value stream. These patterns are critical interactions between the collaborators who plan, build and deliver software at scale:

In the early years of Tasktop, almost all our customers focused on only one or two of these integration patterns – the most popular being the tester-developer alignment. Our analysis, however, revealed that this number has greatly increased as customers expand their integration use cases in exciting and sophisticated ways.

With new business goals and opportunities, companies are often required to add more tools, and consequently more artifacts, into their value stream to adapt and meet these demands. With each new tool or artifact, there are more moving pieces and connections to account for. This results in a more complex set of integrations that can only be created, managed and optimized through Tasktop.

This data has also allowed us to see the future potential that Tasktop could tap into. For example, customers are creatively using more tools outside of their primary intended use, such as using an Agile Planning tool such as CA Agile Central (Rally) for program and project management.

We have already started to define new integration patterns, as well as adapting existing patterns to make more sense for the evolving software development landscape. A common example we have seen with our customers has been the integration of security monitoring tools to integrate vulnerabilities with defects and tests in a quality control tool.

Such customer-centric R&D not only improves our understanding of our product and the market, but increases customer engagement as they begin to see the far-reaching efficiency benefits of end-to-end value stream integration . We can’t wait to see what our customers come up with next!

Have you devised any unusual integration patterns that have liberated your teams from manual effort and awkward collaboration? Or are you wondering how you can use Tasktop to create a workflow that suits your perpetually evolving business? We’d love to hear from you to demonstrate how we can help.