Home > Articles

  • Print
  • + Share This
This chapter is from the book

Managing Integration Teams

There are two basic models for managing integration requirements and supporting software development projects: enterprise integration teams and business model-driven integration. Both models have their own challenges and key success factors. The choice depends on the corporate culture, the number of project teams, and the experience of project management staff.

Enterprise Integration Teams

Usually, the enterprise integration team is a separate team or department with dedicated staff to support it. These teams work at an enterprise level, and are liaisons with departmental and other distributed development project teams. The integration team is tasked with designing the integration infrastructure, setting standards, and working with the other project team leaders who implement the various integration strategies and components.

Enterprise integration teams need to have a broader view of the corporate IT function and the corporate business goals. The challenges faced by these teams include getting support from other project teams in implementing enterprise-level integration requirements. It is not unusual for department project teams to feel burdened with extra work by the enterprise teams. There is often conflict between the short-term goals of department project teams and the long-term goals of enterprise integration teams that result in tension; integration often suffers as a result. Enterprise integration teams rarely succeed without continued support from senior management. Figure 7.2 shows the critical role of project managers in enterprise integration teams. These project managers not only manage specific integration projects but also are responsible for coordinating integration analysis across department project teams.

Figure 7.2 Centralized integration team.

Business-Model-Driven Integration

Another model used in some corporate environments is to define integration requirements based on the business models. When using this model, the business users or business analysts define the overall business integration objectives, and publish a roadmap. Project teams responsible for implementing the roadmap resolve application integration issues by using the common development process. Individual project teams are completely responsible for adhering to corporate standards in their development projects. Project managers collaborate to schedule, estimate, and plan for integration-related enhancements and developments.

This model works well when the number of project teams is small (between one and five), and when the business models are well-defined and documented. For larger numbers of project teams, a central integration team is required to define the standards and ensure compliance across the enterprise. Also, the business models often are not accurate or even complete. The fast-changing business environment makes it hard to define the business requirements and build a stable business model. As a result, frequent changes to integration requirements bog down the project teams affecting the delivery of software.

Figure 7.3 shows the importance of a complete business model when it drives enterprise integration. A complete business model does not have to capture all business processes in the enterprise, but the business processes that are part of the model should be complete. Only then can integration requirements be derived for implementation across project teams.

Figure 7.3 Business-model-driven integration teams.

Advantages and Disadvantages

Both models have their advantages and disadvantages when applied to project-managing strategies. Isolating integration as a separate project enables the integration project teams to focus on developing the integration solutions more quickly. However, the practical value of the integration solution can only be realized when deployed in conjunction with business applications that are developed by different project teams. Many times, the integration solutions developed by dedicated integration project teams are technically good, but they are developed in isolation without full understanding of the complete requirements. The usual causality in these scenarios is the technology, which takes the blame for failed integration projects.

On the other hand, empowering individual project teams with the necessary integration standards and tools doesn't automatically guarantee cooperation between project teams. Many times, the management objectives of individual project teams are focused on departmental issues rather then understanding enterprise objectives. Unless a stable business model is defined, project teams are constantly grappling with changing integration requirements.

Software integration is a cross-functional requirement and cannot be solved by isolating the integration teams; nor can it be solved by allowing individual project teams to function in isolation. One approach that yields better results is training the development teams on integration tools and development methodologies that make integration part of the process. Project managers need to change their project management techniques and processes to include closer cooperation from other project managers, technical leads, business analysts, and integration experts. It is very important that every project team has a technical lead (or an architect, depending on the size of the project) who is a member of an integration team composed of technical and business experts.

In very large global organizations where integration issues are not only technical but also geographical, a central integration council with participants from all geographical regions is useful in determining the challenges of integration. In smaller organizations, integration teams tend to be formed on a more informal basis, with representation from each project team as required for specific time-bound integration projects. Regardless of the type of team and the methods used to form them, participation from all involved application teams and availability of integration experts is critical.

The integration experts need to ensure that all software development activities adhere to common enterprise integration standards, tools, and architecture. We will explore the role of adapters in integration projects more in the following sections.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020