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

Handing over control of a project seems like it might be scary to do when finishing a project for an outside client, as it means that as a developer your product better work as it is intended. This final stage problem, like ease of use and other end user issue have to be taken care of or as a developer you will find yourself with an unhappy customer. How can a developer go about taking care of handing a finished state project off to a client, I will tell you what I have done in handing over a project to a client.

flowchart

Figure 1: The Raw flow of development. By Wesley Eversole

Currently I am handing over a website to a client and a lot of the work the team I am working with has been making sure the client can take care of their website with out needing to go in to the source code. In the paper”Key Factors for Developing a Successful E-commerce Website” by Osama Mohammed Ahmad Rababah and Fawaz Ahmad Masoud, the authors denote the three different areas which are the usability, conceptual reliability and representative reliability. The note that usability is the over all ease of maintaining, navigating adaptability and user friendliness the website offers. These were some of the core ideas we needed to give our website for our client to use. Figure 1 capture a raw essence of what development can be like. There is a loop that a developer must fill to satisfy their customer

When leaving a finished product with a client the developer should put them self in the head space of their client. The developer needs to make sure that they make using their product accessible. In the website I am building we decides on using word press as a launching point since work press has easy to navigate back end. For our client being able to work the website for themselves has been the key development choose we want to work in to the project. There is also the training we need to give our client since we know our client has limit skill in working a website that we have to plan for when handing over the project to them. In this case we have to train the client to be able to log in to the web site and then update pages they need to. The end hope of developing a website like this is to accomplish results like in “Agile for Dummies” written by Scott W. Ambler and Matthew Holitza, Where the IBM team was able increase the presences of the client from around 10 interactions to over 400 for a given project  (p. 58). A level like what is noted in “Agile for Dummies” is the end goal that the team I am apart of would like to accomplish make the client part of our design process. Doing that lets us teach the client so when we leave they will be able to manage their delivered product.

References

Ambler, S. & Holitza, M. (2012). Choosing an Agile Approach. In Agile for Dummies (IBM ed., p. 74). Hoboken: John Wiley & Sons.

Rababah, O. M. A., & Masoud, F. A. (2010). Key factors for developing a successful e-commerce website. Communications of the IBIMA, 2010, 1-9.

Advertisements