How to hand over your project to another software house?

00:00 → 00:02

Handing over a project is a crucial step in the software

00:02 → 00:06

lifecycle and it may turn out to be harsh and costly unless

00:06 → 00:09

you take the right precautionary steps to make it

00:09 → 00:10

smooth and downtime free.

00:10 → 00:14

In this video, I will show you how to transfer your software

00:14 → 00:16

project to another software house.

00:16 → 00:20

First of all, make sure that the choice of the new software house is based

00:20 → 00:23

on the retrospective assessment of your previous team.

00:23 → 00:27

Sharing openly the lessons learned may be a good incentive

00:27 → 00:30

to test a new team against challenges you have faced before.

00:30 → 00:33

The handover process is about transferring both a software

00:33 → 00:35

system as well as knowledge,

00:36 → 00:39

experience and responsibilities required for managing it.

00:39 → 00:42

Such top down knowledge and perfect understanding of your

00:42 → 00:44

business is key to partnership based

00:44 → 00:46

on consultancy,

00:46 → 00:48

responsibility and strong motivation.

00:48 → 00:51

Therefore, except for description of requirements,

00:51 → 00:53

apps architecture or deployment guidelines,

00:53 → 00:56

you should give a new team a general introduction to your

00:56 → 00:59

business goals or strategic knowledge about your users.

00:59 → 01:03

You should also outline what work has been done so far and

01:03 → 01:06

at what stage of the development roadmap you are now.

01:06 → 01:09

A good practice is to allow a new team to perform a code

01:09 → 01:12

review to measure the general health of the application.

01:12 → 01:16

At Merixstudio we test the app against security,

01:16 → 01:18

performance and code quality.

01:18 → 01:22

You can also benefit from time overlap between old and new teams.

01:22 → 01:25

Direct information exchange between engineers may

01:25 → 01:29

facilitate the communication and shorten the feedback loop.

01:29 → 01:31

Our advice is to meet the team in their office,

01:31 → 01:35

maybe during scoping session or product design workshop.

01:35 → 01:39

That's a great opportunity to build friendly relationship

01:39 → 01:42

and a good way to start the development process.

01:42 → 01:46

As you can see, project handover embraces numerous

01:46 → 01:49

processes and it is important to plan it properly.

01:49 → 01:52

If you have any questions related to this topic,

01:52 → 01:53

free to contact us.

01:53 → 01:54

We are happy to talk.