TaskTop, provider of a Framework that leverages APIs to integrate application lifecycle management (ALM), is promoting the concept of a software Integration lifecycle bus. Providing capabilities similar to what an enterprise service bus ( ESB) does for applications, Tasktop is making a case for the integration of ALMs within and without an organization. Img Credit: Tasktop.com With the release today of Tasktop Sync 3.0, the company is extending that integration to IT operations management in the form of integration with IT service management (ITSM) and helpdesk tools—initially in the form of offerings from ServiceNow and Atlassian, respectively.
In addition, Tasktop is extending its ALM support in this release to include integration with ALM platforms from Serena Software and Rally Software. Tasktop is also prepping a beta program from a Tasktop Sync SDK, and has released Tasktop Configuration Templates that define configurations of synchronizations that can be reused across multiple projects. As part of that simplification effort, Tasktop has previously launched an open source project through which run-time code can be directly embedded within an ALM framework. According to Tasktop CEO Mik Kersten, the issue that many organizations have to day is that there are an incredible number of known issues with applications and systems that are getting rediscovered every day. This situation exists because there’s no mechanism in place for passing that information between disparate ALM and IT operations management tools, says Kersten. Rather than trying to integrate all that information database level Kersten says Tasktop Sync provides an integration Platform that leverages APIs and Web Services to seamlessly integrate all the information required to create a truly comprehensive approach to managing DevOps. The primary benefit of Tasktop Sync is that it doesn’t force IT organizations to adopt one set of tools over another. Each unit within the enterprise or outside it can continue to use whatever set of tools they like best, while being able to share all the relevant information needed with other release management or IT operations teams. Organizations are obviously in different states of maturity when it comes to DevOps. But it’s clear they are all heading in the same general direction. The challenge they face is deciding between a forklift approach to DevOps that makes a giant leap forward, or taking a more gradual approach that doesn’t introduce as much of shock to the software delivery system within their organization.