Contents of A Project Proposal Document
Contents of A Project Proposal Document
The second page should contain a declaration on originality of work –duly signed
The main document starts at the fourth page, the contents of which should follow the
following outline.
1. Background
This is usually a detailed background information about the project research area and about
the client. It should be clear on what business the client is involved in and how operations are
currently conducted. It sets the stage for the problems that will arise.
2. Problem Statement
This is a statement of the problem the project is intended to address. It should clearly show
the problem in the light of the project research and its contribution to the solution. Ideally it
should originate from the way the organization currently performs its functions. Each problem
should be stated clearly with a brief explanation on how it arises from the functions be
undertaken.
3. Proposed Solution
This is a high level description of the proposed system touching on major system functionality
or features.
N.B. This should not be a basic statement of automating a manual system.
4. Project objectives
Clear, concise “SMART” objectives should be provided including research and system
development related objectives. They are the basis upon which the success of the project will
be evaluated. Therefore they should basically address each of the problems being faced by the
organization.
5. Literature Review
A survey of literature of earlier works or studies conducted in the researcher’s area of interest
to identify current developments, challenges and gaps that need to be addressed. This presents
a good foundation for the researcher to formulate and concretize their problem.
6. Methodology
This is basically an outline of the plan of action. It encompassess the all-round developmental
methodology driving your entire data collection to system development.
N.B. Avoid using basic lifecycle-related process models e.g. prototyping – these are not
methodologies.
This should generally address all the envisaged resources that will enable the development of
the system to succeed. The key items are hardware, software,human and any other costs that
will be incurred.
8. Project schedule
This is a breakdown of all the tasks that will be carried out in the course of carrying the
project. An estimate of the duration of each task in hours should be done. A work breakdown
schedule should be formulated and a task schedule/Gantt chart prepared.
A sample project schedule is as shown below:
Proposal Dcoument Fromat Page 2
KCA University 2010
9. Conclusion
There must be a conclusion. This states what is likely to be the outcome of the project.
10. References