Delivery Process

You should deliver your product to your customer, in person rather than electronically if at all possible. When you deliver it, you should describe its current status with respect to the original requirements; that is, what works and what doesn't. You should demo the product to your customer and allow him or her to ask questions. If your customer wishes, you should install the product on a machine in the customer environment.

During delivery you should turn over to your customer one or more electronic doucments containing the following information.

1. Release notes giving version number, status, known bugs
2. Installation instructions
3. A User Manual
4. Your Requirements, Design and Test documents from class
5. Any additional technical documentation you think might be useful to subsequent maintainers (portability considerations, design notes, etc.)
6. The source code for the product

All of these items (with the exception of #4, which you have already submitted) should also be linked onto your Swiki team page.

Some common areas of problems are:

1. Poor packaging – customer is given random files with no clear organization, or a confusing zip file.
2. Lack of troubleshooting instructions – what should customer do when things go wrong (both during installation and use of system).
3. Poor code comments, or failure of team to follow consistent coding standard.