Re: Application Development

> 1. What is a reasonable warrenty period for the delivered > application? Depends. From the contractor's point of view, none at all. :-) I'd really reckon it varies from none to 30 days to 90 days. I *am* _very_ biased, I admit, but I've found that 98% of the "bugs" I've encountered were actually due to the client not really knowing whathe/she wanted in the first place. If you have a solid, signed in blood, definitive specification, then you should be able to agree to a 90 day warranty. > 2. If major bugs are encountered after the warrenty period, who > typically pays? The contractor or client? Client. > 3. What is a good method for "signing off" the completion of the > package. What are the major points of agreement and > obligations the vendor and the client must agree to? Depends on the spec. You should be able to sign off each activity from a project plan. But it really depends on the situation. You should agree to functionality, performance and documentation requirements at the very least. > 4. What percentage of the total package cost is a reasonable price to > pay for extended warrenty? 20% per annum? > 5. What other critical points if any should we be examining? Sounds dumb, I know, but do you *really* know what you want? > 6. Are there any good references on this subject? I only know "Banging your head against a brick wall for ten years" by Billy Wheeler. :-} -- Cheers, Billy the proud parent.