The Written Report
The written Project Proposal Report should be between 3,000 to 4,000 words long. It should consist of 1.5 or double spaced typescript, and an appropriate font such as Times New Roman, CG Times or Arial, with text size 12. The page margins should be set as: top 2.5 cm, bottom 2 cm, left 3 cm and right 2 cm. You must also leave an empty line between paragraphs.
Project Proposal Contents
A structure similar to that shown below should be followed for the Project Proposal Report.
Introduce the project and any background which may exist. Briefly describe what the project is all about, what you hope to achieve and how you will achieve it.
If the project is undertaken for a client then you should give a brief background of the client and what the client is expecting this project to achieve (client’s aims). If the project is your choice then explain why the project interests you and what you expect to gain from the project.
The literature review section should be around 1,000 to 1,500 words long, ie approximately a third of the proposal report. Through the literature review you must introduce and provide a good understanding of the theme area of your project. In the early part of the literature review you must focus on the generic area that your project is aiming at and provide a good understanding of this area, what its purpose is, and why it is important. Following that you must identify precisely where within the literature your project fits. You must also elaborate on any relevant social aspects and implications.
To help you clarify the direction that you must take when putting together the literature review try to keep in mind the title of your project along with your ‘Aims and Objectives’.
Ultimately, in Chapter 2 of your Final Project Report, you would be expected to present the ‘Literature Review’ that you have included in the ‘Project Proposal’ but considerably updated to include any other relevant information that you have identified during the whole period of the project.
Dr. N. Ioannides (2010) 3 CT3P50N – Project Proposal Report Guidelines
Aims and Objectives
Identify and explain the overall aims of your project. These should be followed by a list of objectives which should collectively describe what the final deliverables and achievements of the project will be.
When putting the list of Aims and Objectives together you must start by clearly understanding what the title of your project is all about. In order to satisfy the title you must perform several tasks. Split the requirements of the title down to 3 or 4 major tasks. These are your Aims. In order now to satisfy each Aim, several tasks must be performed which once completed will satisfy the requirements of each Aim. These are your objectives. See additional material added to this site:
All objectives must begin with the word ‘to’, and should be phrased so that the success or failure in meeting them can be tested or measured. The best approach to setting objectives is to define a series of smaller objectives, rather than building the project around a single large objective. In this way you can ensure that the project is not dependent on one single objective.
The objectives should cover two areas:
Academic objectives, covering such things as your research objectives, particular theory or
techniques that you will explore and apply, and any required objectives of your course.
Personal objectives, including skills that you are planning to acquire in order to be able to
successfully complete the project
Approach (Scenario / Case Study / Problem Identified)
In this section you must identify how you are planning to approach your project. Will it be based on a scenario, a case study, a problem area, or any other way which will make it possible for you to focus your efforts in finding a solution to your problem and completing your project? For example, if your project is based on building a network for a specific need, then this need must be put into a real world context in the form of, possibly, a case study, a scenario or a problem in need of a solution. In a similar way, if you are working on a consultancy project, you must in a similar way include the requirements of your customer, the relevant background of the work they want done and what they hope to achieve at the end of the day. This will help you put into perspective the work that you will be doing and focus on the desired outcome.
Scope (incl. Methodology, Resources, Boundaries, Assumptions, Risks, Contingency Plans and Constraints)
Describe and justify the activities that you plan to carry out and the limits of your project. Note any project specific assumptions and explain the reasons behind them. Also, the functional or academic boundaries of your project must be included. Functional boundaries help define which parts of a problem will be addressed. In order to clarify the scope and boundaries of the project, it may be helpful to list what you will not be covering. Identify the possible risks that could take place and may jeopardise your project. In each case you must provide contingency plans (fall-back positions). Also, any project-specific constraints should be noted for review. Be specific and avoid bland statements that apply to all projects.
Also, include any skills that you plan to acquire which will enable you to successfully complete your project. You must include a brief justification of your choice of methods and tools. Identify the resources or tools which will be required, highlighting any special ones, in order to enable you to complete your project. You may include any hardware and software necessary.
Project Plan, Major Milestones and Deliverables
The project plan should include two items:
Work Breakdown Structure (WBS) which will identify the list of project tasks that you have to
Gantt chart identifying the scheduling of particular project tasks and should include the work to
be done until the end of your project.
The deliverables should include all of your key development products and research outputs as well as timings of your main deliverables and activities. Ensure that they are aligned with the university’s project submission timetable for CT3P50N.
Final Project Report Table of Contents
A preliminary ‘Table of Contents’ must be provided which will indicate how you are planning to structure the Final Project Report.
References and Bibliography
List of references and bibliography that you have consulted in preparing your Project Proposal Report and also through your Preliminary Literature Review. An appropriate referencing technique, such as the Harvard or the Vancouver System should be used.
You should also indicate what resources (list of books, etc.) you are planning to read and why they are important (what each item has to offer) in your understanding of the specific project field.
The marking scheme for both the Project Proposal Report and the Oral Presentation is shown below. Keep this in mind when you are preparing your work. Ultimately, if you do not include sections which are meant to be marked those sections will receive 0 marks. In short the marking scheme will be:
Literature Review (Criticality, Conciseness, Context, Variety, Connections, etc):
Aims & Objectives:
Approach (Scenario / Case Study / Problem Identified):
Scope (incl. Methodology, Resources, Boundaries, Assumptions, Risks, Contingency
Plans and Constraints):
Project Plan, Deliverables and Major Milestones:
Final Project Report Table of Contents:
References (Evidence of Search, Listing of Refs both within the text and at the end):
15 % 15 % 10 %
5 % 10 % 5 % 10 %
TOTAL MARKS: 70%
English & Presentation (Style, Clarity, Spelling): 5%
Understanding (Do you understand what it is that you are doing?): 15%
Direction (Are you clear and confident regarding the direction you must follow?): 10%
TOTAL MARKS: 30%