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.
·Discuss how you will approach the project (scenario, case study, problem area, other)
·Discuss the methodology that you will follow (explain why it is appropriate)
ØAny specific assumptions (explain the reasons behind them)
ØActivities to be undertaken: Justification and limitations
ØFunctional and/or academic boundaries
·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
·Contingency Plans:
ØAlternative ways to follow in case things go wrong.
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.
The project plan should include the following items:
·Major Milestones – ensure they align with the project module submission timetable
·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.
·Skills – identifying which skills are available and which are required.
·Risks – considering what could compromise the progress and success of the project.
·Work Breakdown Structure (WBS) – identifying the list of tasks that you have to undertake.
·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.
·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 or employers, making 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, premises, etc.)