How to Write Software Project Terms of Reference

Plain English guide to writing project terms of reference

Author: David Tuffley
Length: 11 page(s)
Written: Apr 2011
Sales Rank: - XinXii Sales Rank

Views: 524

Category: Computer & IT » Projekt Management | Work: Guidebook
Keywords: software project terms of reference, software quality, project management,

Practical guide for software development project managers and staff

Introduction

This standard defines the form and content of Terms of Refer-ence documents. These are used to clearly define the objec-tives and deliverables of a given task or function, along with the parameters and constraints within which these objectives are to be achieved. They ensure that the customer of the task or function, the organisation carrying out the work, and the in-dividual responsible for that work clearly understand the objec-tives, deliverables, parameters and constraints of the task or function.

A terms of reference can apply to a wide-ranging, multi-resourced study to be carried out, right down to describing in-dividual areas of responsibility. For example, terms of refer-ence may be produced for a steering committee, a project, a project manager, or a task of work. In some instances, terms of reference may even be used in lieu of a project plan and quality plan.

Scope
This standard defines the format and content of all Terms of Reference documents.

Objectives

The outcome of using this standard will be the following.

• All QMS projects or work will have documents that clearly define the objectives and deliverables of a given task or function and the parameters and constraints within which these objectives are to be achieved.
• All Terms Of Reference documents shall be consistent in format and content.

Flag

Seller assumes all responsibility for this listing.

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.