{"id":810,"date":"2014-11-12T18:50:29","date_gmt":"2014-11-13T02:50:29","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/Can-Polarion-39-s-All-In-One-Unified-ALM-Solution-And\/ba-p\/380941"},"modified":"2026-03-26T05:31:16","modified_gmt":"2026-03-26T09:31:16","slug":"can-polarions-all-in-one-unified-alm-solution-and-integrations-coexist","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/can-polarions-all-in-one-unified-alm-solution-and-integrations-coexist\/","title":{"rendered":"Can Polarion&#039;s All-In-One Unified ALM Solution And Integrations Coexist?"},"content":{"rendered":"<p>Have you ever played &#8220;the telephone game&#8221;? The one where there\u2019s a group of people, and somebody whispers a message to one person, who whispers it to another, and so on around to the last person. That <STRONG>last person<\/STRONG> invariably receives a <STRONG>different message<\/STRONG> than the first one, sometimes with a totally <STRONG>different meaning!<\/STRONG> When I was a child I looked forward to the final result because it was always funny.<!--more--><br \/>\n<P style=\"text-align: center;\"><A href=\"http:\/\/community.plm.automation.siemens.com\/legacyfs\/online\/siemensplm_blogs\/2014\/11\/company-telephone-game.png\" rel=\"nofollow noopener noreferrer\"><IMG class=\"alignnone  wp-image-6798\" src=\"http:\/\/community.plm.automation.siemens.com\/legacyfs\/online\/siemensplm_blogs\/2014\/11\/company-telephone-game.png\" alt=\"Illustration: the telephone game\" width=\"654\" height=\"291\" \/><\/A><\/P><br \/>\n<P style=\"text-align: center; font-style: italic;\">The Telephone Game<\/P><\/p>\n<p><H2>The Software Development Game<\/H2><br \/>\nI worked once in a company that had lots of tools. It was a <STRONG>tools chaos!<\/STRONG> Every team used a different one, there was no communication across them. I would write my requirements in one tool, the developers would use something else, and the QA team yet another one. QA had access to my tool to mark the requirements as done. I had hardly any visibility in the other tools. There was literally <STRONG>no way to trace<\/STRONG> all the implementation details. We relied a lot on verbal communication.<\/p>\n<p>The result was all too often a scenario like this: my project manager informed me that a requirement was not implemented as requested, but it was marked &#8220;done&#8221;. When I raised the &#8220;problem&#8221; in a meeting of senior managers, the engineering chief got miffed. &#8220;It&#8217;s marked as done. There&#8217;s no problem. You&#8217;re wrong!&#8221; In the absence of data, s\/he who is higher up the power ladder wins. I felt like I was playing the telephone game, except it wasn&#8217;t fun anymore. When the stakes are high, garbled communication can hurt you.<\/p>\n<p>Have <I>you<\/I> ever been in difficulty because of the lack of complete information across tools? What\u2019s the solution for connecting the silos and accelerating collaboration, integrity, innovation? Is it even possible?<br \/>\n<H2>&nbsp;Barriers to \u201cbetter\u201d<\/H2><br \/>\nWhen I joined Polarion two years ago I discovered its <A href=\"http:\/\/www.polarion.com\/products\/alm\/\" rel=\"nofollow noopener noreferrer\"><B>unified ALM solution<\/B><\/A> for all the teams I was working with. Everything that I needed was in one place. I felt relieved, I felt protected from entering into another difficult situation like I had been in before. I wished I had had Polarion years ago.<\/p>\n<p><STRONG><STRONG>&nbsp;<\/STRONG><\/STRONG>But despite the clear benefits, reality is that the companies face many barriers in adopting a single, unified ALM solution. Let\u2019s look at the main ones:<br \/>\n<UL><br \/>\n\t<LI>The <STRONG>agile practices<\/STRONG> that are very popular today give teams<STRONG>autonomy<\/STRONG> and self-organization. Therefore they can choose their preferred tools. When the teams are geographically distributed, or are part of different departments, there\u2019s even more chance for them to choose different tools.<\/LI><br \/>\n\t<LI>\u201cThe shortest path is the one that you know\u201d. Many people are <STRONG>reluctant to change<\/STRONG>, even to a better solution, because they don\u2019t like to go out of their comfort zone, or they <STRONG>fear the short-term costs<\/STRONG> involved in disruption and training.<\/LI><br \/>\n\t<LI>Organizations rarely start with a vision of massive enterprise deployment; instead, they seek to solve specific problems. As a result, they end up with several <STRONG>overlapping solutions<\/STRONG> rather than a single unified one.<\/LI><br \/>\n<\/UL><br \/>\n<H2>\u201cDon\u2019t take away my tool!\u201d<\/H2><br \/>\nPeople love their tools&#8230; and for quite good reasons. How many times in my career has a colleague come to me very excited about an &#8220;amazing tool!&#8221; s\/he had found? <I>Lack of tools<\/I> isn&#8217;t the problem. What&#8217;s missing is a way to <I>connect tools<\/I> to provide full-spectrum information for the entire product team. People do want to use preferred tools, but not as <I>disparate<\/I> tools. They want them work together <I>like<\/I> a single solution&#8230; one that lets them <B>work the way they want to and still have the benefit of complete, relevant information<\/B>.<\/p>\n<p>Excited as I was about Polarion, it became clear to me that integration with other tools was still needed. More than 30 extensions were a proof that Polarion was already addressing this need. The question was, to what extent?<br \/>\n<H2>What\u2019s wrong with extensions?<\/H2><br \/>\nOne of the things that I did was to look at the analysts:<br \/>\n<UL><br \/>\n\t<LI><B>2011 Ovum:<\/B> \u201cALM integration has been a perennial problem in the industry.\u201d (Software Lifecycle Management 2011)<\/LI><br \/>\n\t<LI><B>2012 Forrester:<\/B> \u201cALM vendors have acknowledged the inevitability of integration with other commercial and open source tools. However, we\u2019re a long way from arriving at a common integration strategy that makes it easier for customers to select ALM tools based on their individual merits outside of integration\u201d. (The Forrester Wave\u2122 Application Lifecycle Management Q4 2012).<\/LI><br \/>\n\t<LI><B>2013 Gartner:<\/B> \u201c[Integration] while tools provide the basic facilities, the pictures are often better than reality.\u201d (MQ for ALM Nov 2013).<\/LI><br \/>\n<\/UL><br \/>\nAll analysts had consistent reports: there were unresolved challenges with <I>integration<\/I>.<\/p>\n<p>Why were they saying that? What was wrong with the extensions?And then came the \u201ca-ha!\u201d moment. There was nothing wrong with the extensions&#8230; they were just not enough. There was a lack of focus on the <I>integration<\/I>. What Polarion needed was to change our approach: instead of seeing integration as a mere \u201cextension\u201d, we needed to make it an important piece of our unified solution. We needed an <STRONG>integration strategy<\/STRONG> that would make it easier for us and our partners to build new integrations and actually make them <STRONG>work together like one solution<\/STRONG>.<\/p>\n<p>And so we started to engineer the <STRONG>Polarion Integration Platform<\/STRONG>. What is so special about it?<br \/>\n<H2>\u201cConnecting the dots\u201d<\/H2><br \/>\nTraditionally, integrations connect applications through so called \u201cpoint-to-point connectors\u201d. Their problem is that the cross-tool communication is difficult because they communicate in pairs only, and the implementation and maintenance are costly because they require development for each pair of tools.<\/p>\n<p>Polarion\u2019s integration platform uses an <STRONG>integration bus<\/STRONG> to connect the applications.<br \/>\n<P style=\"text-align: center;\"><A href=\"http:\/\/community.plm.automation.siemens.com\/legacyfs\/online\/siemensplm_blogs\/2014\/11\/polarion-integration-bus.png\" rel=\"nofollow noopener noreferrer\"><IMG class=\"alignnone  wp-image-6799\" src=\"http:\/\/community.plm.automation.siemens.com\/legacyfs\/online\/siemensplm_blogs\/2014\/11\/polarion-integration-bus.png\" alt=\"Illustration: Polarion Integration Bus concept\" width=\"342\" height=\"322\" \/><\/A><\/P><br \/>\n<P style=\"text-align: center; font-style: italic;\">Polarion&#8217;s Integration Bus concept<\/P><br \/>\nBecause data is managed centrally and not in multiple points, the communication across the applications is easier and more robust. Development and maintenance are faster and easier because you only have to build the connection to the integration bus to get out-of-box access to the other integrated applications.<\/p>\n<p>The beauty of this architecture is that you don\u2019t need to care about any other applications that may be integrated on the platform. This opens new possibilities: end-to-end traceability across multiple tools, a central way to define conflict resolution mechanisms, process automation and centralized dashboards.<\/p>\n<p>Our vision is for Polarion to offer you an <B>umbrella solution,<\/B> meaning <I>a complete ecosystem addressing any software development need<\/I>.<br \/>\n<P style=\"text-align: center;\"><A href=\"http:\/\/community.plm.automation.siemens.com\/legacyfs\/online\/siemensplm_blogs\/2014\/11\/polarion-umbrella-solution.png\" rel=\"nofollow noopener noreferrer\"><IMG class=\"alignnone  wp-image-6801\" src=\"http:\/\/community.plm.automation.siemens.com\/legacyfs\/online\/siemensplm_blogs\/2014\/11\/polarion-umbrella-solution.png\" alt=\"Illustration: Polarion ALM as an umbrella solution encompassing integrations\" width=\"558\" height=\"365\" \/><\/A><\/P><br \/>\nWith the new Integration Platform we give you a <B>unified integration solution<\/B> that will accelerate integration. You will be able to give your teams autonomy, to contain your costs, and to work with your tools as with one single solution. By connecting the silos you will have access to complete and accurate data so that you can make the best decisions. The telephone game will finally disappear from your organization, or it will be only a fun game for your team building events.<\/p>\n<p>This exciting innovation is coming your way along with <STRONG>Polarion version 2015<\/STRONG> early next year. Find out more about this release on our <A href=\"http:\/\/www.polarion.com\/2015\/\" rel=\"nofollow noopener noreferrer\">Polarion 2015 Early Access Program microsite<\/A>.<\/p>\n<p><HR \/><br \/>\n<P style=\"text-align: center;\"><STRONG>&nbsp;DOWNLOAD FREE WHITEPAPER:<\/STRONG><\/P><br \/>\n<P style=\"text-align: center;\"><A href=\"http:\/\/www.polarion.com\/resources\/download.php?dl=Accelerate-Innovation-with-Unified-Application-Lifecycle-Management-ALM.pdf&amp;utm_source=integrationPlatformAnn&amp;utm_medium=web&amp;utm_campaign=blog\" rel=\"nofollow noopener noreferrer\"><IMG class=\"alignnone\" style=\"border: 1px solid #ccc;\" src=\"http:\/\/www.polarion.com\/resources\/img\/covers\/Accelerate-Innovation-with-Unified-Application-Lifecycle-Management.png\" alt=\"Whitepaper: Accelerate Innovation with Unified Application Lifecycle Management\" width=\"273\" height=\"389\" \/><\/A><\/P><br \/>\n<P style=\"text-align: center;\"><A href=\"http:\/\/www.polarion.com\/resources\/download.php?dl=Accelerate-Innovation-with-Unified-Application-Lifecycle-Management-ALM.pdf&amp;utm_source=integrationPlatformAnn&amp;utm_medium=web&amp;utm_campaign=blog\" rel=\"nofollow noopener noreferrer\">Accelerate Innovation with Unified Application Lifecycle Management<\/A><\/P><br \/>\n&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Have you ever played &#8220;the telephone game&#8221;? The one where there\u2019s a group of people, and somebody whispers a message to one person, who whispers it to another, and so on around to the last person. Tha&#8230;<\/p>\n","protected":false},"author":55815,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[],"industry":[],"product":[],"coauthors":[],"class_list":["post-810","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/810","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/users\/55815"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/comments?post=810"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/810\/revisions"}],"predecessor-version":[{"id":811,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/810\/revisions\/811"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/media?parent=810"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/categories?post=810"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/tags?post=810"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/industry?post=810"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/product?post=810"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/coauthors?post=810"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}