project proposal

Applicable to Studies and Assessments

Note: these guidelines particularly apply to projects which explore topics and problems with the object to identify and create conclusions and solutions.  While this information might apply to projects which generate a product, the information is designed to assist students who do not intend to create one.

PLEASE DOUBLE SPACE!!!!!!!!!!!!!!! 12 font (not the default Word 2007 11pt font)

Do NOT use first person, no “I” no “we”

Keep your writing formal – no contractions, spell out acronyms, etc

Project Proposal Document:  (follow this structure EXACTLY.  Include these headings)

Project Name - this should be unique and descriptive.  It should be short and concise.  Do not chose a name that is in bad taste.  Be specific.  For example, don't say "Project to implement new technology."  This is too general and could apply to almost anyone

To be Completed by: your name

Executive Summary - describe the project and goals in a short, understandable language.  Include a specific problem statement which clearly identifies the specific problem.  Then include a specific solution statement which clearly identifies what you will do to solve the problem.  For example: 

    "The problem is xx hospital is spending large amounts of money on imaging service contracts.  This project will explore this problem, searching for lower cost alternatives.  This project will propose a specific strategy to lower imaging service costs."

Avoid the use of technical or industry specific terms.  Keep this section simple, accurate and clear.  Overall describe what the project will accomplish on a high level (avoid all detail).  Describe the broad focus and overall goals. Be VERY careful - length is important.  Your executive summary should be no longer than one paragraph.  It should NOT be a bulleted list.  It should NOT include the steps you will take to complete the project.  It is likely that you will essentially summarize your deliverable(s).  This section should be able to be read and understood without reading any other parts of the proposal.

Assumptions - describe the assumptions made about technology, the people involved and the expenses involved.  The assumptions are things like: this project will examine only three vendors at the request of the staff...or... this project will not examine long term training needs as the project duration will be limited to one year...

Stakeholders - identify the clients and any other people who may be interested or impacted by the project..be fairly specific, don't say "everyone at Community Health network" - clearly not everyone will use the new equipment

The problem - define the problem to be addressed as narrowly as possible.  You probably need a sentence that says "The problem is...."  Include as much detail as possible. You may need to describe problems which are identifiable but would be difficult (too large, expensive) to include in your project.  These specific extra issues are "out of scope" but should be mentioned.  Be specific.

Proposed solutions or conclusions/deliverables - describe how the problem will be solved.  It is the foundation for your work so it must be comprehensive, unambiguous and very specific.  Be clear so the reader knows how each problem will be solved.  This section should contain enough high level detail and technical specifications so that the project seems feasible.  Use active sentences:  This project will examine...this project will explore...this project will implement...this project will evaluate...DO NOT simply redescribe the problem.  A bulleted list works nicely here

Project Objectives - objectives are precise, detailed and measurable.  Define exactly what the project must achieve.  Use enough project objectives to define the project fairly concisely.  It is unlikely that two or three will be satisfactory.  You DO NOT need to identify HOW you will carry out the objectives in this section.

Developmental Methodologies describe the activities, technical, research and creative which will implement the project objectives.  What software will be used?  Is there hardware involved?  How will data be collected?  It is best to examine each project objective and HERE explain how this will be handled.

Constraints, limitations and risks what limits the project?  Examples of constraints include equipment, scheduling, people, cost and scope.  Include any opportunities for events or changes (risks) which would impact the project during the development.  These should apply specifically to you and your project.  For example, do not include global issues such as overall budgeting of an institution or other wide ranging hurdles.  Stick to the boundaries of your project.  For example, explain the limits of your research (I will only investigate these three departments).  This section should carefully outline the boundaries of your project. 

Project Phases, Milestones and intermediate deliverables identify specific deliverables.  Milestones are not necessarily deliverable dates but are points in the project where major achievements are made.  They are checkpoints throughout the duration of the project.  This may be a table but should include a fair amount of detail - not just a bulleted list.  One or two sentences ARE NOT ACCEPTABLE.  You are encouraged to establish measurable and realistic deliverables. For example, if an objective is to improve staff satisfaction, you should reword this to be specific, “staff interviews/surveys will indicate improved satisfaction with xxx.” Concrete deliverables which use words like “create” “quantify” and “prepare” along with items like reports can be identified when complete. Some students and their mentors struggle to determine when a project is finished. Identification of concrete deliverables (rather than “better workflow” or “improved communication”) can tremendously impact the ability to label a project as complete. This section is likely the largest part of the proposal.

Costs prepare estimates of expenses.  If gathering data is part of the project, say so

Quality Assurance and Testing Processes and Procedures describe how the project will be assessed.  Discuss how the final outcome will be evaluated and by whom.  How will specific results be determined?

Summary  The summary should be at least several paragraphs and should include the major points of all the information above.  This section should be able to be read and understood without reading any other parts of the proposal.  It is a bit repetitive but it should draw from almost all sections previously prepared.