Vendor Transition

We gather all the necessary information for a thorough assessment of your operation’s current status; this usually implies on-site visits and face-to-face meetings but can also be done virtually. Namely, we set up meetings with relevant stakeholders, explore your organization’s pain-points, read all pertinent documentation, examine your infrastructure, discuss management / development / delivery / release processes, etc. Afterward, based on our findings, we present an effective plan to achieve your company’s vendor transition objectives. This includes defining a roadmap, determining the new team’s structure, and writing up an architecture diagnosis document.

This is an adaptation period where information is transferred from the old vendor to the new. Project documentation, access to source code, assets, development/production environments, and deployment/management procedures are some of the aspects involved in this stage. Generally, this is executed by the core team that participated in the discovery phase, guaranteeing continuity, and allowing accrued knowledge to be capitalized upon throughout the entire transition process.

The new team, defined during discovery, takes charge of all on-going development and maintenance efforts. The core team - those who went through the knowledge transfer - ramp up the new team members based on the established roadmap, using artifacts and processes defined during stage two. This continues until dependency on the old vendor team is eliminated and the new team flies solo, taking over completely.