Blog 8: Handing off a project to a client; what are the risks and challenges?

You think that by having completed coding on your project and finished bug testing you are done? Not so fast! The final task for your team is successfully handing the project over to the client. Sounds easy? It can be depending on the project. A simple app for a cell phone? Just upload it to a App store with a description and you are done. But for a larger project, one that is not going to be on a app store, things are going to get a little more tricky.

First and foremost, what are you going to hand over to the client? Are you going to send them every single thing you worked on? “The choice of what to do with production graphics is up to you. Some designers keep their original, editable versions of their graphics. Others hand over all the files.” (Karl, Sahlin).  The most important thing to understand is that whatever you send you should always keep a copy for yourself and that you should document for the client exactly what you are handing over and why.

The next hurdle you must cover when handing over a project is how much support are you going to give the client? Are you going to train them on your whole application? Chances are that the client might not know how to use your program so at the very least you will need some sort of documentation on its workings.

How is the client going to get the application or program anyway? Are you going to transfer it by a disc? is it going to be a direct download somewhere? Are you using a app store? If like in my teams case its a website Karl and Sahlin write, “ Best practice is to deliver the site itself to the client’s web server via FTP (File Transfer Protocol).” Although it may seem pretty basic you need to have a plan on how to send the completed project to your client.

There are probably countless issues you can have delivering a completed project to your client. To minimize any problems take extra care in creating your documents and action plans in the deliverables. This will save you a major headache in the end when all you probably want is to be done with it.


Images from:–cronological.htm

Sahlin, Doug, and David Karlins. Building Websites All-in-one for Dummies. 3rd ed. Hoboken, N.J.: Wiley, 2012. Print.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s