How to Write Software Project Agreements

Plain English guide to writing project agreements

Author: David Tuffley
Length: 24 page(s)
Written: Apr 2011
Sales Rank: -
Views: 388

I N T R O D U C T I O N

How to Write Software Project Agreements defines the terms of the agreement between the Customer and the Developer, specifying the products and services to be provided by both parties, the specifications for products, and the delivery time and cost information.

Such an agreement is essential to the successful execution of any project, and forms the basis upon which all work is performed. The project agreement is the internal equivalent to a commercial contract.

Normally the Project Agreement makes reference to other documents which provide the detail for specific areas. When this is done the version numbers of these supporting documents is stated so that they cannot be changed without requiring a change to the Project Agreement.

How to Write Software Project Agreements defines the minimum content, format and presentation of a project agreement.

O B J E C T I V E S

The outcome of using How to Write Software Project Agreements will be the following:

Identify the responsibilities of both the developer and the customer, during the life of the project
Define the financial arrangements between the customer and the developer
To document the terms of the agreement between the cus-tomer and developer so that each clearly understands what work is to be performed for what cost
To enable a formal change control process to be applied to the project
Contribution to IS Quality. It has long been recognised that without a clear, documented agreement as to deliverables, cost, and schedules, the likelihood that disputes will arise between customer and developer rises sharply.

Research has also shown that where a clear and comprehensive agreement has been reached at the outset of the project, its chances of success, in terms of meeting the customer's needs, on time, within budget, also rises.

How to Write Software project Agreements is a plain-English, procedural guide to developing first rate project agreements. It contains detailed instructions and templates.

About the Author

David Tuffley
Member since: Apr 2011
Publications on XinXii:  25

My social profiles on...

David Tuffley PhD is lecturer and researcher at Griffith University in Australia. David is a Software Engineer, though his interests range across Comparative Religion, Philosophy, Psychology, Anthropology, Literature, History, and Architecture.

David has been an academic since 1999. Before academia he was a consultant for public and private sector IT clients in Australia and the United Kingdom. He combines theory and practice in a focussed and disciplined way that has proved effective for solving problems for clients.

No review yet.