You need to sign in to do that
Don't have an account?
Stephen O'Reilly
Handover Document
Hi there,
What would be a suitable handover document to expect from a developer who has just completed an integration with a backend system and Salesforce? It's a fairly big custom integration and we wanted to make sure that we have documentation so that we could give it to another developer and they could get up and running with it quickly. There isn't much of a design document for this project. Would anyone have an examples of this kind of document or templates etc. Any direction would be greatly
appreciated.
What would be a suitable handover document to expect from a developer who has just completed an integration with a backend system and Salesforce? It's a fairly big custom integration and we wanted to make sure that we have documentation so that we could give it to another developer and they could get up and running with it quickly. There isn't much of a design document for this project. Would anyone have an examples of this kind of document or templates etc. Any direction would be greatly
appreciated.
Scott Nelson Solutionist
Depends on the what type of integration it is. Most common items are object lists, class definititons, field mappings, activity and sequence diagrams or at least detailed narratives. It also often depends on whether the developer is an FTE or contractor or consultant, though IMO it really shouldn't :)