One response is to consolidate all lifecycle tools from a single vendor. A common vendor gives the best chance of getting an integrated development and support solution. The problem is that most organizations—for a variety of reasons—simply cannot do that. They can’t just rip out tools from disciplines that have mature practices in place, even if they wanted to. Sometimes they can migrate from the old to the new. But even those situations require a transition period where both systems must coexist for at lease some amount of time. So the challenge is, how does one gain the benefits of practicing ALM and yet retain operational use of tools that are in place and working well enough? Doing so requires that the tools interacts in a way such that data from one tool can be traced to related data in another tool (traceability). Doing that will provide users in one discipline insight into data created and managed by other users in different but related disciplines with the tools that they use (visibility). And in doing all of that, users across disciplines can find more efficient and effective ways to work together in the overall software delivery process (collaboration). The key to making all of this happen is lifecycle tool integration. And its been done over the years in many different ways. The problem is that those ways of integrating aren’t working very well—especially across tools stemming from a variety of sources.
Before we begin even talking about the Rational Lifecycle Integration Adapters, let’s see if it even makes sense for you to care. See if the conditions stated above apply to your current selling situations. Where they do apply, you’re in a position to use a coexist strategy to the account. This strategy has you sell only a portion of the Rational ALM solution and use integration adapters to connect to the customer’s other ALM products. Doing so allows you to Contain the competing solutions from further growth into other functional areas Brings in some amount of revenue where none was in play before Establishes or increases your account presence Buys you time to earn new reasons of call for selling more value down the line
Developing integrations in-house No commercial tools—all open source, tools integration team dedicated to developing integrations Change in staffing, budget cuts, need to pull valuable resources into developing business-critical apps New versions of tools require significant integration re-work =&gt; Can’t upgrade tools! LL: Developing integrations is hard—maintaining integrations is harder! Working across disparate organizational boundaries One company outsourced components of software required for total solution Crates a supply chain of dependency Data flow business critical, but cannot affect tools or processes of vendors LL: Need a way to collaborate across disparate organizational lines
Key to an administrator&apos;s ability to manage an organization’s integrations landscape is visibility into the synchronization usage occurring. Understanding things like high volume time periods, repositories that have the most artifacts being synced and integrations that produce the highest load of synchronizations allows you to properly plan and manage your entire integrations landscape. We do this by providing macro views and statistics that are dynamic and interactive, allowing administrators to proactively manage their integrations landscape. Key Benefits Macro visibility into key statistics allows better control and management of your integrations What systems get the most usage? How &quot;much&quot; collaboration is happening between silos? How significant is your non-primary tools usage? Dynamic filtering and searching allows for flexibility into the macro data available, ensuring you can see the data that is most important to your organization Easy access via a web UI ensures everyone who should view this data can with ease
No cost for this option for IBM customers. Virtual training access limited to 1 administrator. Larger support packages available for a fee.
Taking agile development to enterprise scale in a mixed tool environment with the Rational Lifecycle Integration Adapters