Integrated Delivery Center

Integrated Delivery Center (IDC)

Today’s projects require close coordination and cooperation of people, on both customer side and services provider’s end, creating the right balance of business, domain and technical expertise.  This wide assortment of strong business domain and technical skills cannot be found in just one location. We need better business and communication models to facilitate coordination and cooperation of people for successful project delivery, we tried to achieve through Integrated Delivery Center model.

Through this model, Bering Labs help technology firms setup their own remote delivery teams which are managed by a management layer with the right blend of business, management and technical expertise, thus freeing the client’s IT leadership team to concentrate on more strategic concerns. The management layer structure is designed to mitigate communication, language and cultural issues and have the right co-ordination between stakeholders and offshore delivery teams. It will help to deliver more tightly managed projects that arrive on time, on budget and in alignment with client requirements.

Remote delivery teams will have better understanding of client’s requirements, business, operating challenges and most importantly domain knowledge to successfully execute projects.This layer will explain and manage project requirements, oversee project execution and deliver the project.

Integrated Delivery Center has two important components.

  • Management Layer
  • The Project Lifecycle Management System

Management Layer

Management layer which consists of an Onsite Client Partner, A Business Analyst and Offshore delivery manager. Onsite Client Partner is local resident with a strong industry background and who is able to understand client’s culture, operating processes, challenges and business goals. Once the project kicks off, he will work closely with Offshore Delivery manager and Business Analyst to manage remote team and make sure project is delivered according to the client’s need.

The Business Analyst with domain knowledge will understand and elicit project requirements by using a Industry Standard Requirement Analysis Framework. This requirement analysis framework provides clear cut guidelines, tools and checklists for precise requirements elicitation.

The Offshore Delivery manager will oversee the project delivery from Bering Labs offshore delivery unit and ensure that IT services are delivered with precision and customized to the client’s particular needs.

The Client Partner, Delivery Manager and Business Analyst will be in consistent communication, working in lockstep to make sure Bering Labs offshore team operates as a physical and virtual extension to the client’s IT organization.

Project Lifecycle Management System

We standardise project delivery teams on a single system which includes project management, collaboration and communications facilities to bring transparency, visibility and control. The system provides complete visibility to clients in real time and they can monitor and track the progress of their projects and the developers they hire. The progress is easily visualized and measured with project metrics, charts and projections.

This provides a centralized environment where all the stakeholders – executives, managers, product owners, scrum masters, developers, and testers – can easily work together regardless of location.

The IDC model addresses typical challenges of distributed delivery such as transparency, visibility, control, delayed response, IP Protection, time-zone/cultural differences, talent retention, etc.

Important Features of the IDC model

  • Built upon the philosophy of “co-development”, “virtual teams” and “white-box” execution (as against an outsourcing-themed black-box models)
  • Use an Iteration Planning Meeting Tailored for Remote Sites.
  • We Separate teams by functionality not activity.

  • Have Each Site Send Ambassadors to the Other Sites.
  • Use Continuous Integration to Avoid Integration Headaches.

  • Use Test Scripts to Help Understand the Requirements.

  • We Never Underestimate the Culture Changes and Issues.

  • Use Regular Builds to Get Feedback on Functionality.

  • Use Regular Short Status Meetings.

  • Use wikis to contain common information.

  • Use Short Development Iterations.

Request a Free Quote

All fields are required*

Your Name

Your Email

Your Subject

Your Message