{"id":1409,"date":"2016-03-31T05:04:42","date_gmt":"2016-03-31T05:04:42","guid":{"rendered":"https:\/\/www.kovair.com\/blog\/?p=1409"},"modified":"2016-03-31T05:04:42","modified_gmt":"2016-03-31T05:04:42","slug":"kovair-omnibus-the-tale-of-a-project-managers-companion","status":"publish","type":"post","link":"https:\/\/www.kovair.com\/blogs\/kovair-omnibus-the-tale-of-a-project-managers-companion\/","title":{"rendered":"Kovair Omnibus – The Tale of a Project Manager\u2019s Companion"},"content":{"rendered":"

\"Project
\nJohn Smith, a project lead in an MNC, has been managing software projects for a decade now. A typical weekday in John\u2019s life means hours of grueling meetings with various stakeholders, astronomical heights of stress to meet strict deadlines, and gallons of caffeine with extra sugar.<\/p>\n

But that is a year-old story from now. It was during then that John came across a software product by Kovair named \u201cOmnibus Integration Platform<\/a>\u201d. The product promised to create an information flow across the organization and break down the silos that might have existed. However, to John, the product and the assurance given by it seemed too good to be true.<\/p>\n

A year later, with Kovair Omnibus, John\u2019s typical weekday consists of less number of meetings, no last minute surprises, easy-to-meet deadlines, and less or no caffeine. This begs a question as to what were the problems faced by John and how Kovair Omnibus became a savior for him.<\/p>\n

John\u2019s problems a year ago<\/h2>\n

Like everyone, John used one of the best-known PPM tools to manage the bits and pieces of Projects as iterations and subsequently the user stories. The same tool wasn\u2019t applicable for developers who were working in the IDEs like Eclipse and Visual Studio. To convey the user stories to developers, John used to have weekly meetings, if not on a daily basis. For tracking the progress made on the user stories, the developers had to create copies of them in their SCM tools. Once development was done, manual notifications and continuous follow-ups from either side was needed. To worsen the situation, Testers – the perceived arch enemies of Developers – had no idea about the development activities, until it was time for release.<\/p>\n

\"John<\/p>\n

Figure 1:<\/strong> John’s Problems a year ago<\/p>\n

All these conditions led to several productivity and delivery related challenges to John which were difficult to resolve. Some of them are as follows:<\/p>\n

1. Siloed Development <\/strong><\/p>\n

Cross-functional teams like Dev, QA and Release didn\u2019t share the same set of priorities between each other which resulted in a huge information gap with no a<\/p>\n

ccess to real-time actions. As a result John, as a PM, had to manually intervene for setting up uniform order of deliveries. This affected the entire delivery process adversely.<\/p>\n

2. No Automated Workflow<\/strong><\/p>\n

In order to streamline the Development and the Project Management process<\/strong><\/a>, defining a common and automated workflow across the project was a necessity. Since all the tools used by cross-functional teams were disconnected, defining a common workflow that spans across multiple tools wasn\u2019t feasible.<\/p>\n

3. Lack of Traceability<\/strong><\/p>\n

The information gap between the cross-functional teams often made the essential work items like User Stories, Changesets, and Defects as discrete objects. This was a massive concern for John. He had no easy methods to quantify the Dev activities or QA activities going on, or the number of bugs raised with respect to any User Story. This often led to deliveries of inferior quality.<\/p>\n

4. No central reporting mechanism<\/strong><\/p>\n

With each of the teams working in their own tools environment, there was no centralized reporting mechanism. This meant that in order to quantify the progress of a particular project, John needed to collect data from each of the Team Leads and form a report manually.<\/p>\n

\r\n

Enterprise Tools Integration and Data Synchronization<\/h2>\r\n
Live Product Demo by our Experts<\/div>\r\n
\r\n Get Demo<\/a>\r\n <\/div>\r\n<\/div>\n

Then John meets Kovair<\/h2>\n

One day, while browsing through the SD Times\u2019 list of top 10 ALM<\/a> and software development tools, John came across the name of \u201cKovair\u201d among other ALM tools in the list. Upon visiting Kovair website<\/a> pages, he came to know about an integration product called \u201cOmnibus Integration Platform\u201d which has the capability to integrate 60+ ALM\/SDLC tools off-the-shelf<\/a>. The integration as John came to know about was carried out using an SOA based ESB Architecture called Omnibus Engine. It made John wonder if adopting this new integration platform would be the solution of his Project Management ordeal. He promptly requested for a live demonstration to Kovair. The Solutions Engineers from Kovair demonstrated a simple Project Management Use Case to John for his better understanding.<\/p>\n

Use Case scenario:<\/h2>\n

A Project Manager creates a Project in CA Clarity tool. The Project gets reflected in Rally. In Rally, several iterations are planned. Some user stories are created and assigned to those iterations. The Development activities done with respect to the user stories would be carried out in Eclipse and stored in SVN Repository. The QA activities would be managed in HP ALM, while bugs would be tracked in JIRA. John wanted an integration between all these tools so that the information barrier and, thereby, the cross- functional tool and team silos could be removed. Little did John know he would be witnessing more surprises than he imagined.<\/p>\n

What John saw\u2026?<\/h2>\n

In the demo, John saw that as and when a Project was added in Clarity tool, the same Project got replicated in Rally. In Rally, several iterations were planned with respect to the Project. Several user stories were created and assigned to the iterations. The user stories were visible in both Dev and QA tool, i.e. Eclipse and HP ALM, respectively. Kovair used a plug-in for Eclipse, using which data from any tool integrated via Omnibus were visible and accessible from the Eclipse IDE. All these happened without John having to store the data manually. Similarly, the Rally user story got automatically created in the QA tool with the help of Kovair Omnibus. To John\u2019s amazement, he saw that as and when the test execution failed in HP ALM, a Bug got automatically submitted to JIRA. John came to know that it was possible due to the built-in functionality of Kovair ALM tool \u2013 \u201cKovair Policies\u201d or \u201cBusiness Rules\u201d. With time, John explored other advantages of Kovair Omnibus.<\/p>\n

\"automated<\/p>\n

Figure 2:<\/strong> An automated cross tool workflow with Kovair<\/p>\n

    \n
  1. Configurable Integration Rules: <\/strong>The integrations, as John came to know, were being carried out using an Event-Action based mechanism. This signifies whenever an event happens; for e.g. an Object being created in Tool A, it triggered the creation of a similar Object in another tool. This event action based mechanism could be defined with a few mouse clicks from Kovair Application.<\/li>\n
  2. An automated configurable cross-tool workflow clubbed with notification:<\/strong> John learnt that with Kovair\u2019s workflow engine, he could automate several Project Management processes which would otherwise require manual interventions. For example, on completion of every development and QA phase, an automated email notification as well as a task in the user\u2019s to-do list got created for the team members of the next activity, including John, eliminating manual interactions and hand-offs.<\/li>\n
  3. Support for Data Synchronization and Federation: <\/strong>In the demo, <\/strong>John also saw how to move and replicate data across different tools with the real-time synchronization capabilities of Kovair Omnibus. \u00a0In addition, Kovair\u2019s linking capability helps users create virtual links which makes viewing and accessing of data possible without replicating and storing them across the tools.<\/li>\n
  4. Cross Tool Reports and Metrics: <\/strong>John understood that he could use Kovair tool as a central repository and store all the cross-tool data to define and create various reports, metrics and KPIs. It would help him with better decision making and streamlined Project Management in the future. As a cherry on a cake, these reports were also configurable with simple mouse clicks.<\/li>\n<\/ol>\n

    \"Monitoring<\/p>\n

    Figure 3<\/strong>: Monitoring Multiple Projects from a Single Screen in Kovair<\/p>\n

      \n
    1. Data Sync Monitoring Capabilities:<\/strong> John could also view the information getting synched between different tools in real time. In case, the sync session fails due to any of the tools being non-operational or out of network, John knew that he didn\u2019t need to worry about it. He would immediately get a notification about the cause of failure.<\/li>\n<\/ol>\n

      John\u2019s Life now a year later\u2026<\/strong><\/h2>\n

      John did a brief evaluation of the tool with a few of his team members before purchasing the Kovair Omnibus Integration Platform. After few hours of training on the product usage, John and his team members could easily manage the Kovair product all by themselves. Today, John is much confident about meeting his delivery deadlines and achieving project targets. He has also made a significant contribution towards improving software quality and delivery. The team silos gradually broke down, giving the way to more collaborative development efforts.<\/p>\n

      Now John and his team can focus more on enhancing quality which was not possible earlier due to long meetings and follow-ups. His countless hours of grueling meetings, sleepless nights, stress and caffeine with extra sugar have come to an end.<\/p>\n

      Conclusion<\/h2>\n

      Share your tools integration pain points with us and we will help you to solve with Kovair Omnibus. Kovair currently has 60 out-of-the-box integrations with tools from various domains like ALM, ITSM or Help Desk. For more information about Kovair\u2019s integration capabilities, please visit our website www.kovair.com.<\/a><\/p>\n

      \n
      \n
      \n

      Get Started with Kovair Omnibus<\/strong>, mention your requirements<\/p>\n<\/div>\n

      Get FREE Demo<\/a><\/div>\n<\/div>\n<\/div>\n
      \r\n
      Related Posts<\/div>\r\n
      \r\n\r\n
      \r\n
      \r\n \r\n\r\n \"Zero-Downtime\r\n\r\n <\/a>\r\n <\/div>\r\n\r\n \r\n Zero-Downtime Data Migration Strategies for Financial Institutions (2026 Guide) <\/a>\r\n\r\n <\/div>\r\n
      \r\n
      \r\n \r\n\r\n \"Data\r\n\r\n <\/a>\r\n <\/div>\r\n\r\n \r\n Why Data Migration Fails Mid-Project (And How to Prevent it Before you Write a Line of Code) <\/a>\r\n\r\n <\/div>\r\n
      \r\n
      \r\n \r\n\r\n \"Cross-Platform\r\n\r\n <\/a>\r\n <\/div>\r\n\r\n \r\n Legacy Native to Cross-Platform Migration: What to Reuse and What to Rebuild <\/a>\r\n\r\n <\/div>\r\n \r\n <\/div>\r\n\r\n