Project Proposal Report
Template and Guidelines
(V.2022.Feb)
The Proposal Report is one of the most important deliverables of any project. Its intention is to define the scope, approach and plan of work which must be undertaken for successful completion of the project. It provides a firm foundation for executing the project and acts as a baseline for monitoring and managing progress, thus improves the possibilities of a successful project completion.
A Project Proposal Report should clearly describe the following:
What you are planning to do.
Why you have chosen to do it.
How you are planning to achieve it.
Who will be doing what?
When you are planning to do it.
Proposal Report Specification:
Length: 2,000 to 2,500 words long (excluding References and Appendices)
Line spacing: 1.5 lines
Font type: Calibri, Arial, Helvetica, Verdana, or Times New Roman.
Font size: 11.
Page Margins: top 2.5 cm, bottom 2 cm, left 2.5 cm and right 2 cm.
1 empty line must be left between paragraphs
Upload the Project Proposal Report on Moodle (Turnitin submission)
Name the file as: StudentID-Surname-Firstname-Project-Proposal
Use the following pages as a template for your proposal and follow the guidelines provided in each section. The intention is to help you plan your project work and present it in a structured and logical format.
Once your Project Proposal Report is ready you must:
Delete the specifications pages so that the cover page becomes the front page of your report.
Delete all the guidelines provided and only leave your writings.
Assets of Quantum Computing and its Exposures in Real World (font 16 & bold) |
Project Proposal Report |
Insert your Title, Name and Surname (font 14) |
Insert your UoR ID number (font 12) |
Insert you UoR email address (font 12) |
Supervisor: Insert your supervisor’s Title, Name and Surname (font 12) |
Insert your supervisor’s QA email address (font 12) |
Faculty of Computing |
BSc Computing Technology |
Dissertation |
DD MMM YYYY
Enter your Project Title here again
Introduction and Project Context
In this section you must:
Introduce your project (what is it about), the type of applied project it may be (academic, consultancy, practical), and define any terminology if required (briefly explain it).
Provide justification on the choice and its importance, who will benefit, what is the specific purpose.
Provide an in depth focus on the background circumstances which indicate a need for the specific applied project that you propose and discuss the importance of the problem, issue, need, opportunity, requirement, shortcoming, impairment, etc. that you intend to tackle here. If done for a client, introduce the client as well and what they hope to achieve.
Address the current body of knowledge concerning the topic proposed to demonstrate that you know a great deal about the specific issue that you focus on. Bring forth information from existing sources (cite them) regarding the specific topic (such as graphs, charts, and statistics, if available).
Ethical, Social, Legal, Professional Issues.
Aims and Objectives
Here, you must identify and explain the scope and overall aims of your project. The Aims should be followed by a list of objectives which should collectively describe what the final deliverables and achievements of the project will be.
This section must include:
Introduction to the overall intention behind the project
Aims (4 to 5 aims each focusing on a specific part of the project)
Objectives (3 to 5 objectives for each Aim thus providing enhanced focus and clarity on the direction to be followed)
Deliverables (what the final outcome of the project will be)
When putting together the list of Aims and Objectives, you must start by clearly understanding what is the intention behind the project. The title must represent very clearly the focus of the project (by reading the title, a reader must know clearly what the project is all about).
In order to satisfy the title you must perform several tasks. Split the requirements of the title down to 4 or 5 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 that specific Aim. These are your objectives.
Ensure that your Aim and Objectives are SMART:
Specific: well-defined and focused
Measurable: ways of knowing when the goals have been achieved
Attainable: can realistically be achieved
Relevant: must relate to the initial intention and expected deliverables
Timely: must be completed on time
The structure of the Aims and Objectives is shown in Figure 1:
Figure: The structure of Aims and Objectives
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. Typical Command verbs that could be used are shown in Table 1 below:
Table: Command verbs to use in the Aims and Objectives
To analyse … To apply … To assess … To calculate … To compare … To construct … To create … |
To demonstrate … To design … To develop … To differentiate … To discuss … To evaluate … To establish … |
To estimate … To explore … To investigate … To justify … To plan … To predict … To produce … |
To propose … To recommend … To research … To review … To secure … To simulate … To validate … |
DO NOT USE to understand to find to learn to know |
The best approach to setting the scope and direction of the project is to define 4 or 5 Aims, each with a series of smaller and focused objectives (3 to 5), rather than building the project around a single large Aim. In this way you can ensure that the project is not dependent on a single Aim or a single Objective.
Methodology
In this section you must identify how you are planning to approach your project and include a brief justification of your choice of methods and tools. Whether it will be based on a scenario, a case study, a problem area, or any other way, the approach that you choose to follow must 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 or creating a mobile application for a specific need, then this need could 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 consider the requirements of your client, 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.
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. Also, any project-specific constraints should be noted for review. Be specific and avoid bland statements that apply to all projects.
In this section you must:
Discuss the methodology that you will follow (explain why it is appropriate)
Discuss how you will approach the project (scenario, case study, problem area, opportunity, other)
Discuss and justify what activities will be undertaken
Constraints:
Restrictions that define the project’s limitations
Boundaries, as set by the Aims and Objectives
Assumptions:
Events or influences on your project which you perceive to be true without providing any proof that they are actually true.
Project Plan
The project plan should include the following items:
Skills List
Identify the skills required for the project, what is their purpose and your level of capability in using those skills – use Table below.
Table 1: Skills List, Purpose and Availability
Skills |
Purpose |
Capability Level |
Resources list – identifying the purpose behind each item listed 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. Use the Table below.
Table 2: Resources List, Purpose and Availability
Resource |
Purpose |
Availability |
Work Breakdown Structure (WBS) – identifying the list of tasks that you have to undertake and should be based on your Aims and Objectives.
Major Milestones – ensure they align with the project module submission timetable
Gantt chart – Identifying the scheduling of particular project tasks and should include all the tasks which must be undertaken until the end of your project – use the relevant spreadsheet in the ‘Project Planning Tools’ Folder in Moodle.
Risk Register – Identify and record any risks that could compromise the progress and success of the project, include mitigation and contingency plans – use the relevant spreadsheet in the ‘Project Planning Tools’ Folder in Moodle.
Examples of Risks:
Non-availability of resources (journals, library facilities, IT facilities, laboratories, specialist equipment, etc.)
Tasks that overrun due to lack of experience (in estimating their duration, or in applying them to a real-world situation)
Other commitments (coursework, employers, unexpected demands on your time)
Unexpected or higher than anticipated costs (if applicable)
Concerns on Client-based Projects (lack of access to clients, business documents, etc.)
Summary and Conclusions
This section must include:
Summarise what this project is about
Briefly revisit the problem, requirements or opportunity that this project will attempt to tackle
Highlight the benefits from tackling the problem, requirement or opportunity
Revisit what the intended deliverable from the applied project will be
Briefly discuss what would the next steps be
References
List of references and bibliography that you have consulted in preparing your Project Proposal Report and also through your Preliminary Literature Review. The Harvard referencing technique must be used (see guidelines on Moodle).
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.
Appendix A
Ethical Approval Form
This form must be completed, signed and submitted with the Project Proposal.
No work may be carried out on the project until the form has been submitted.
Late submission will result in a penalty.
Failure to submit the form will result in an automatic fail for the module. You may also be subject to disciplinary action.
Section 1 TO BE COMPLETED BY STUDENT |
|||||||
Name of Student: |
|||||||
Student No: |
|||||||
Course: |
|||||||
Module: |
|||||||
Project Title: |
|||||||
Summary of Proposed Project: |
|||||||
Planned Start Date: |
Planned End Date: |
||||||
DECLARATION BY STUDENT: I confirm that I have read and understood the Research Ethical Guidelines and agree to abide by them in conducting my project. I confirm that I understand the importance of adhering to the Research Ethical Guidelines and I am aware of the penalties for breaching them. I agree to notify my academic supervisor if there is a change to my project and/or further ethical approval is needed. |
|||||||
To the best of my knowledge, I confirm that: There is no risk to any participants There is no risk to me There is no risk to the institution or QA in terms of liability or reputation |
|||||||
I undertake to report all data and findings in a responsible way |
|||||||
Name: |
Signature: |
Date: |
Section 2 TO BE COMPLETED BY SUPERVISOR |
||||||
Name of Supervisor: |
||||||
DECLARATION BY SUPERVISOR: I undertake to review and approve any questions that the student intends to use for data collection, including interview questions and questionnaire items. |
||||||
ON THE BASIS OF THE INFORMATION PROVIDED BY THE STUDENT, THE PROJECT: |
||||||
DOES NOT need to be referred to the Faculty Research Ethics Committee for approval. |
||||||
DOES need to be referred to the Faculty Research Ethics Committee for approval. |
||||||
If the project needs to be referred to the Faculty Research Ethics Committee for approval, please explain why briefly: |
||||||
On the basis of the information provided by the student, I confirm that the project will contain sensitive or confidential information and should not be placed in the public domain. |
||||||
Name: |
Signature: |
Date: |
Section 3 TO BE COMPLETED BY SUPERVISOR |
|||||
CHANGES TO PROJECT – DECLARATION BY SUPERVISOR: I have reviewed the proposed changes to the project. |
|||||
ON THE BASIS OF THE INFORMATION PROVIDED BY THE STUDENT: |
|||||
I APPROVE the revised project. |
|||||
I DO NOT APPROVE the revised project. |
|||||
If the revised project is not approved, please explain why briefly: |
|||||
Name: |
Signature: |
Date: |
Section 4 TO BE COMPLETED BY STUDENT |
|||||
CHECKLIST FOR STUDENT |
|||||
I have fully completed this Ethical Approval Form and have signed where appropriate. |
|||||
I have included a copy of any research instruments I wish to use (interview questions, questionnaires, etc.) in the Appendix of my proposal. If draft versions, I undertake to have the final versions approved by my supervisor before collecting any data. |
|||||
I have included this Ethical Approval Form in the Appendix of my proposal so that it may be reviewed by my supervisor. The proposal outlines the research methodology I will use. |
|||||
I have included this Ethical Approval Form in the Appendix of my dissertation. My supervisor has completed Section 2 of this Ethical Approval Form and has signed where appropriate. |
|||||
Name: |
Signature: |
Date: |
Appendix B:
Any documentation necessary to support the proposal must be included in the Appendix.
- Assignment status: Already Solved By Our Experts
- (USA, AUS, UK & CA PhD. Writers)
- CLICK HERE TO GET A PROFESSIONAL WRITER TO WORK ON THIS PAPER AND OTHER SIMILAR PAPERS, GET A NON PLAGIARIZED PAPER FROM OUR EXPERTS
