What to do in the handover process?

The following tells you what to do in the handover process

The main theme is that when a request coming, you know enough to do your job. where the server is. How to compile all the code? How to deploy? Know who to ask for support, e.g. infrastructure support.

Initial meeting -> Handover meetings -> Handover closer meeting

* Initial meeting. Who is who? What is our goals?

* Another way to think about it. Where is the test? The test scripts will tell the business process.

* When will the warranty period finish? Who will determine if the case come to Management Services or the Delivery team?

* Wiki page requirement: This documentation should be completed to a level where a developer could setup a development environment, make changes, test and release the changes to UAT and Live. Use the Support Handover questions to guide you in the sort of information required.
+ Where is the code in tfs
+ Grant us sufficient tfs permission and remove permission of developer.

* We must retain all project documentation plus the dev environment. Not allow the delivery team to delete anything.

* Dev environment - Can the dev environment be setup successfully by import customisation or import org?

* Seen through the code and see the code in action in its environment/platform

* Find out the overall business process with the requirements in mind.

* Where are the servers?

* Where are the environment?

* Solution diagram

* How do the users use the system? For example, A CERA user creates an contact -> A CETAS user ticks an assessment check box -> Hit save -> A workflow will generate a household record automatically.

* Be careful with any SHARED projects or resources.

* All the Source Code is checked in, can be built successfully and deploy successfully too. Basically, the entire source code base need to be downloaded to a separated computer and build and deploy.