<Project Name>

Terms of Reference

Project Team Name: <Project Name>

Business Relationship
Manager:
Business Owner:
Delivery Date: <Estimated date that this project needs to be delivered by >
Reporting Dates: <Timeline for key deliverables>

1 Problem Statement
<Provide the wider organisation audience with an introduction and overview of the problem, stating
what it is about, why it came about, who is involved, where it is located etc.>

2 Mission
<Provide a broad overview what the project deliver, the benefits that will be achieved and the
alignment with the divisional plan. How the organisationand/or the Business Unit’s business will
be different on completion of the project, that is, what major business activity is going to change as
a result of this project and how? There is no need for in depth detail, keep this part brief, simple,
concise and clear.>

3 Goals
<Define the goals for this project/initiative>

4 Boundaries
<Define the boundaries for this project/initiative and specify any items that are out of scope or will
not resolved>

5 Other Issues
<Provide details of issues that need to be resolved by this project>

6 Key Stakeholders
<List the Key Stakeholders and their roles, in relation to this initiative>

Page 1 of 3
File: 19677652.doc Last Updated: 16 July 2009
 <Project Name>
Terms of Reference

Role Name Division

7 Solution Guidelines
<Provide details of how the solution will be developed, for example Business Requirements and
Business Case to be completed, including estimated dates>

8 Estimated Costs

Item Low $’sK High $’sK Comments

Estimated Costs – <Estimated costs to be completed.
Completion of Business Include any comments that justify your
Case estimates and if applicable, the
breakdown between internal and external
costs>

Estimated Costs – < Estimated costs to be completed.

Development Costs Include any comments that justify your
estimates and if applicable, the
breakdown between internal and external
costs>
Estimated Costs – < Estimated costs to be completed.
Infrastructure Costs Include any comments that justify your
(hardware and software) estimates and if applicable, the
breakdown between internal and external
costs>
Total Estimated Costs <total of <total of
the the
above> above>

8.1 Assumptions
<Clearly document any assumptions you have made in formulating your estimates. For example,
the solution will be developed using only the current computing environment. The solution does
not require any system integration with external parties.>

Page 2 of 3
File: 19677652.doc Last Updated: 16 July 2009
 <Project Name>
Terms of Reference

8.2 Risks
<Identify any high level risks associated with the estimates provided and delivery of the project.
The three main categories of risk factors identified as contributing to the risk of a project or the
probability of project failure are the business environment, the project team environment and the
product or service complexity.>

9 Definitions
<Define any specific Terms and Abbreviations that have been used throughout this document>

Term or Abbreviation Details

10 Appendix
<Include any existing supporting documents or other information as required>

Page 3 of 3
File: 19677652.doc Last Updated: 16 July 2009