IT Integration Team and Fulfillment Integration Team - Clarifying Roles
Summary
With the creation of the Integrations Engineering team in IT there is some cross-over and uncertainty related to responsibilities, communication and partnership with the Fulfillment Business Integration team.
Team Missions
IT Integrations Engineering
- DRI for the architecture, infrastructure, monitoring, auditing, and security of integrations for the enterprise applications ecosystem. This includes data integrating between systems and coming in and out of the systems.
- Working closely with business partners to stabilize, improve and automate their business processes driving efficiencies and supporting an efficient end to end cycle time.
- Achieve SOX and other compliance objectives in our enterprise application eco systems by establishing and maintaining standards for integration infrastructure, access controls, change management, security, monitoring and auditing.
Fulfillment
- Ensure integrity, reliability and stability for non-enterprise application systems within the purchasing and provisioning ecosystem
- Improve the completeness and lovability of purchasing and provisioning
- Reduced turn-around time on business critical work
Sales Systems
Scope of Responsibilities
Systems
Decisions related to the technical architecture of the purchasing and provisioning ecosystem, including services, applications, monitoring and systems is owned by the Fulfillment team.
Decisions related to the technical architecture of the enterprise application ecosystem, including services, applications, monitoring and systems is owned by the IT team (with collaboration from SFDC team where applicable).
Decisions related to crossover between the purchase/provisioning flows and enterprise apps, namely decisions related to the integrations should be discussed jointly between IT and Fulfillment with Fulfillment being the DRI.
Dev Work
The segregation of duties can be thought of in relation to where the impacted code lives.
Noting that if we inserted an API layer between the Customers portal and the Enterprise Applications, the DRI of the receive from API to Enterprise App would change.
Code origin | Fulfillment | IT: Integrations team | Salesforce team |
---|---|---|---|
Customers portal | DRI | - | - |
License app | DRI | - | - |
GitLab | DRI | - | - |
Integration: Customers portal to Zuora | DRI | Contributor/MR Reviewer | - |
Integration: Zuora to Customers portal | DRI | Contributor/MR Reviewer | - |
Integration: Customers portal to SFDC | DRI | Contributor/MR Reviewer | Contributor/MR Reviewer |
Integration: Customers portal to License App | DRI | - | - |
Integration: Customers portal to GitLab | DRI | - | - |
Integration: GitLab to Customers portal | DRI | - | - |
Integration: Customers portal to Marketo | DRI | Contributor/MR Reviewer | - |
Integration: SFDC to Marketo | - | Contributor/MR Reviewer | DRI |
Integration: SFDC to Zuora | - | Contributor/MR Reviewer | DRI |
Integration: BambooHR to Netsuite | - | DRI | - |
Integration: SFDC to Zendesk | - | - | DRI |
Project Cross-Over
When either team embarks in a project (even if just discovery) which could influence or impact the integrations, data or services between the customers portal and the enterprise applications, it is incumbent upon that team to transparently document the goals of the project and to form a working group to include the other team (and potential SFDC) in the discussion from the start.
This will ensure all teams are in agreement with the problem to solve, can provide inputs and evaluate solutions in unison.
Team Nomenclature
There is opportunity to more clearly align each team's role by better defining the names of the team.
IT's Integration Engineering
team leads one to believe this is a team within the engineering organization. Whereas Engineering's Business Integration
team leads one to believe the team sits on the business (or non-engineering) side of the house.
I'd like to propose renaming these teams to make the mission and responsibility as clear as possible.
A potential solution:
- IT:
Enterprise Application Integrations
- Fulfillment:
Fulfillment - Infrastructure, Efficiency & Self-serve