Integration

Nearly all solutions that we deploy need to interact with at least one other existing system, even if that is not a known requirement up front. Examples of common integration points are:

• Security (Authentication/Authorization) infrastructure
• Databases
• Other applications
• External organizations

We have a repeatable process for approaching integration. Early on in the project lifecycle (often during the pre-sales process), we identify the external touchpoints that we need to work with. Then, once we identify all the systems that need to be integrated with our solution, we walk through the following steps for each integration touchpoint:

• We read any available documentation and talk to the experts.
• We write small proof of concept programs to test or validate our assumptions.
• We determine a risk mitigation strategy if issues arise during the proof of concept testing.
• We share the outcomes of our integration results with project stakeholders as soon as practical.

Existing systems are the infrastructure that keeps the lights on for our customers. These applications (and the people that support them) are important assets, and we treat them as such. We are sensitive to the interpersonal and political challenges that legacy integration and/or technology refresh projects pose to IT organizations, and we conduct our engagements accordingly.