Project Proposal Template
Project Proposal Template
Project Proposal Template
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
AMWA <strong>Project</strong> Title<br />
Executive Summary<br />
Executive summary text goes here. Explain in business terms what the purpose of this project is<br />
in a concise summary which is meant to be read by senior business executives. Length should be<br />
about two paragraphs, but this will depend upon the project. Be sure to list the desired outcome<br />
and business benefit.<br />
<strong>Project</strong> objectives<br />
<strong>Project</strong> objectives go here. These should be specific objectives which are measurable, obtainable,<br />
and which can be accurately described:<br />
Objective 1 text<br />
<br />
<br />
Objective 2 text<br />
Objective 3 text<br />
Business context<br />
This section describes the industrial sectors that this project is targeted towards and the people<br />
who will be working on this project.<br />
Industry Sector<br />
This project is primarily intended to benefit the following industrial sector(s) [the following are<br />
examples – please use your own]:<br />
Professional media organizations who need to keep copies of content for long periods of<br />
time (ten years or more)<br />
Developers who create archives and other long-term storage products<br />
Software developers writing applications which exploit archived material<br />
People<br />
Please identify the types of people who will be required to perform this work – if you need<br />
software developers, please say so. If you expect people with hardware expertise to be required,<br />
likewise, please mention them. If you need end-users to participate, please identify what sort of<br />
end-user participation is required, and whether you need users with technical expertise, business<br />
expertise, or some other skill set.<br />
Deliverables<br />
This should be a very specific list of deliverables which will be produced as a result of the<br />
successful completion of the project. Failing to produce these deliverables would signal an<br />
unsuccessful project. If the project is anticipated to take a long period of time, or if the exact list<br />
of deliverables cannot be determined at this time, please list the deliverables that are expected<br />
through the first set of SCRUM Sprints. Large projects may be broken up into multiple phases,<br />
with the level of specificity becoming less granular in later phases.
The following deliverables will be produced by this project:<br />
Deliverable 1<br />
Deliverable 2<br />
Deliverable N<br />
Tasks and estimates<br />
The following is a list of tasks along with estimates, measured in days, of how long each task<br />
would take in ideal days. An ideal day is one in which a person could invest 100% of their time<br />
on the project without any interruptions.<br />
[Note: at this point, a rough outline is fine. Note also that the ‘who’ column does not need to be<br />
completed for every task now, but that it will need to be completed for every task by the time the<br />
proposal is approved. In cases where the work is not accomplished through the firm commitment<br />
of personnel, the AMWA requires specific dollar estimates for resources that would be hired for<br />
the project. Note also that project management needs to be included as an item in any AMWA<br />
proposal]<br />
PHASE 1<br />
Write project statement<br />
Create Specifications<br />
File specification<br />
Another specification<br />
<strong>Project</strong> Management<br />
Total Phase 1<br />
PHASE 2<br />
The second part of this large project<br />
Work that is farther out and which we cannot estimate as accurately<br />
More work as above<br />
<strong>Project</strong> Management<br />
Total Phase 2<br />
who effort Amount<br />
NOTE: Items with asterisk (*) are rough estimates and will be re-estimated during Phase two.<br />
Under ‘who’, JD = John Doe, JA = John Anyone<br />
Resource Commitments<br />
This section of the proposal should specifically list any commitment of resources that is made in<br />
order to further the work of the project. Commitments should be specific and should include<br />
supporting documentation (email or other informal communications is fine).<br />
- Company A commits to provide Engineer A at one day per week and Manager B for one<br />
day per month for a six month period (see attached email from Company A).<br />
- User B commits to provide Business Person A at two days per week for the first month<br />
and then commits to provide that same resource for ½ day per week for the following five<br />
months (see attached letter from User Company B)<br />
Author: Brad Gilmer Page 2 of 2<br />
brad_gilmer@amwa.tv<br />
Last saved 5/10/2012 4:21:00 PM
Change language