1 / 8

The Sign Off Process

The Sign Off Process. Balazs Igli James Edmond Scott McLellan. Presented By:. Agenda. We’ll address the following concerns regarding the sign off process: What exactly is a sign off document and why bother? How is a sign off sheet organized?

liam
Download Presentation

The Sign Off Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Sign Off Process Balazs Igli James Edmond Scott McLellan Presented By:

  2. Agenda We’ll address the following concerns regarding the sign off process: • What exactly is a sign off document and why bother? • How is a sign off sheet organized? • What are the developer’s obligations to the client upon completion of the project? • What kind of support or training should be offered to the client subsequent to the project hand off?

  3. Sign Off Process • The sign off sheet is a legal document stating that the requested system functionality has been completed by the developers; as stated in the project proposal • It is primarily used to protect the developers from potential scope/feature creep after the projects completion • As well it can be useful if a client refuses to pay for the service based on dissatisfaction with the product • It is often a good idea to go through this process several times through the course of the project, usually before each major milestone

  4. Sign Off Sheet Anatomy Client Details Developer Details Project milestone to be signed off on Final agreement Client signature

  5. Obligations to the Client • All of the functionality outlined in the original project proposal must be completed and operational • The system must be ready for implementation on the clients physical infrastructure • All required user documentation must be provided • Also any training documentation (tutorials, whitepapers, videos, etc…)

  6. Client Walkthrough and Training Walkthrough • How to install the software • Day to day use of the application • Administrative user interface explanation • How to generate reports • Any maintenance that the software might require Training • Tutorials • Help documents • Classroom • Online • Paper Manuals

  7. In Conclusion… • The sign off process is imperative for the project to end successfully • It is often a good idea to have the client sign off on every major milestone through the course of the project development process • By having the client sign off your ensuring that your project is progressing in the right direction • In the event the client is not satisfied with the agreed upon requirements of the project you can always resort back to previous sign off documents

  8. The End Any Questions?

More Related