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

Figure 1

After hard working in a project for a long time, it may be exciting when you hand off the project to your client. However, before delivering your project, you need to be careful of the risks and challenges.

• Hand off your project on time

Handing over your project before the deadline is really important. Every project has clear deadline which indicates when you must hand off the project. The client can refuse the project if it is late. For this reason, if you cannot finish the project on time, talk with your client, show your progresses, and get an agreement with another deadline.

• Deliver your project within the budget

Another reason that a client may turn your project down is that the project is out of the budget. Thus, while you are doing the project, you need to be aware of the expenses of the project. If it exceeds the budget, you need to show reasons and get another agreement with your client. Otherwise, it is your responsibility for the exceeded payment.

• A working and functionality required software

You should hand off a working and functionality required software to your client since no client will accept a project which does not fulfill the requirements. Thus, before you hand off your project, you need to have a checklist with each requirement, test and record them one by one. You need to keep the document and show it to your client.

Figure 2

• With the satisfaction of your client

Although you do all above, your client is not satisfied with your project somehow. It may be the wrong style or taste, but the major problem is because of your lack of communication with your client. Steve Berczuk (2013) suggests using Agile methods to avoid it since they “are one way to use iteration and frequent feedback to manage risk.” In Agile, you need to release you project in each Sprint, and your client need to give feedback about the project and sign an agreement, so he/she will not be “surprised” on the day when you hand off the project.

• Training

Training the client is an important step before you hand off your project. According to the experience of Steve Berczuk (2013), “much of the future success of your project depends upon the ends users knowing how to use the process or the system you have been working on.” Thus, a complete document about how to use the software and client training plan are necessary for a successful project.

• Keep a copy of your project

When handing over the project to your client, it is a good idea to burn your final project into two DVDs, and you and your client keep each copy. Sometime the client will give feedback and ask you to follow up the project. You also need to keep all the information about the project because it is the evidence of your work.

• Sign an agreement

You and your client need to sign an agreement while you are handing off the project. Since there is not perfect software, sometimes your client will ask you to response to the bug or maintain the system. You can list them in the agreement and ask for a maintaining fee. In addition, if there are some accounts or passwords related to the project, you need to provide and ask your client to change. Once signing the document, it means your client accepts what you have done.

Being aware of the risks and challenges, you will hand off your project successfully.

 

References

Berczuk S. (2013). How Using Agile Can Help with Risk Management. Retrieved from www.agileconnection.com. http://www.agileconnection.com/article/how-using-agile-can-help-risk-management.

Ben Ferris (2012). How to Hand Off a Project Successfully. http://www.cobaltpm.com. Retrieved from http://cobaltpm.com/project-hand-off/.

Figure 1. Retrieved from http://www.2wtech.com/wp-content/uploads/2013/06/handoff.png.

Figure 2. Retrieved from http://www.net-translators.com/sites/default/files/images/blog/localization_project_handoff_checklist.jpg.