This document defines a project and outlines what information should be included in a project definition. It states that the project definition should include: 1) Background information on why the project is needed and what problem it aims to address. 2) Specific and measurable project objectives. 3) Desired outcomes of the project. 4) What is in and out of scope for the project. 5) Any constraints and assumptions that could impact the project.

1. 1 |
Contents
Project Name
CONTENTS
Project Product Description
Project Definition
1 3
Outline Business Case Project Approach
2 4
5 Project Management Team Structure
6 Role Description
7 References

2. 2 |
Project Definition: what the project needs to achieve?
Project Name
* The targets must be SMART: Specific, Measurable, Achievable, Realistic, and Timely
** DSV initiatives/projects should always support our four strategic priorities: customers, growth, operational excellence and people. Allocate the 100% as either 0% - 25% - 50% - 75%- 100%
1
BACKGROUND
• A description of why the project is being suggested?
• Who wants it & short description of what is expected to be delivered?
• What are the problems/challenges? What is the current situation and what it will be if
nothing is changed?
PROJECT OBJECTIVES
Covering time, cost, quality, scope & risk and benefits performance goals
- what are the specific objectives for the project? These may be to introduce
new IT systems, financial outturns, timings, improvements, etc. within the
organisation; efforts to comply with legislation or reduce complaints, save costs,
boost sales etc.
This will be further described in the Business Case section.

3. 3 |
Project Definition: desired outcomes
Project Name
Project Definition
Desired
Outcomes
- The results of the change derived from using the project’s output.

4. 4 |
IN SCOPE FOR DISCUSSION NOT IN SCOPE
Project Definition: scope & exclusions
Project Name

5. 5 |
Project definition: Constrains& assumptions
Project Name
* The targets must be SMART: Specific, Measurable, Achievable, Realistic, and Timely
** DSV initiatives/projects should always support our four strategic priorities: customers, growth, operational excellence and people. Allocate the 100% as either 0% - 25% - 50% - 75%- 100%
ASSUMPTIONS
CONSTRAINS
Constraints are the restrictions or limitations (external or internal) to the project, which are beyond your control. Constraints are
not negotiable! ex. Technical constrains
Resources, organization, competency, start-up time, technology?
• Which assumptions have you put in place,
in order to predict/estimate correct outputs?
Which preconceptions have shaped your
choices and approach, etc.? e.g. the
application is fit for purpose yy; the
currently running project will establish xx;
for the xx creation zz can do the job, etc.
Assumptions are always at work when we
are defining the: who, what, how and when.

6. 6 |
Project Definition
What the project needs to achieve?
The user(s) and any other known interested parties
• Who are they? Name and roles?
Interfaces
• Interfaces to other systems or projects
Project tolerances
• What can the business case withstand? When do we have to raise an exception to the corporate or programme board?
Constrains & assumptions
• Resources, organization, competency, start-up time, technology?
• Which assumptions have you put in place, in order to predict/estimate correct outputs? Which preconceptions have shaped your choices and approach, etc.? e.g. the application is fit for
purpose yy; the currently running project will establish xx; for the xx creation zz can do the job, etc. Assumptions are always at work when we are defining the: who, what, how and
when.