Comments on: How to Write a Project Proposal http://www.pmhut.com/how-to-write-a-project-proposal Tue, 21 May 2013 15:03:57 +0000 http://wordpress.org/?v=abc hourly 1 By: Baia http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-65853 Baia Thu, 08 Dec 2011 14:32:02 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-65853 I'd like a copy of a project proposal seeking donor funding for an impact project such as water supply project in a developing country like Papua New Guinea. I’d like a copy of a project proposal seeking donor funding for an impact project such as water supply project in a developing country like Papua New Guinea.

]]> By: sherzad. M.permosa http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-30150 sherzad. M.permosa Fri, 24 Dec 2010 17:25:28 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-30150 Project Information Project: PROJECTNAME Project Time-frame: STARTDATE - ENDDATE Attached worksheets: Plan > Resource needs Related Documents: Project proposal > Target audience and benefits Software development methodology Glossary Process impact: This plan will be used to evaluate and manage the project. Key assumptions that affect the plan should be documented here. The project plan should be updated throughout the life-time of the project. TODO: Fill in the information above and below. Add or remove rows as needed. Use the worksheet to help identify and scope resource needs. Summary of Project ONE OR TWO SENTENCES HERE. For more information see the Project proposal. IF YOU PLAN TO ORGANIZE YOUR WORK ACCORDING TO A ROUGH BREAKDOWN OF SOFTWARE COMPONENTS, BRIEFLY DESCRIBE THOSE COMPONENTS HERE. FOUR TO TEN BULLETS. Summary of Methodology What general development approach will be used? THREE TO FIVE SENTENCES OR BULLETS HERE. COVER GENERAL APPROACH, IMPORTANT ASSUMPTIONS, KEY PRACTICES, AND PROJECT COORDINATION CONTROLS. For more information see the Software Development Methodology. How will the project team be organized? The development team will consist of ... The change control board will consist of ... What development and collaboration tools will be use? We plan to use the following tools extensively through out the project: * Project website * Project mailing lists * Issue tracking system * Version control system * Automated build system * Automated unit test system How will changes be controlled? * Requests for requirements changes will be tracked in the issue tracker * The change control board (CCB) will review requested changes and authorize work on them as appropriate * After the feature complete milestone, no new features will be added to this release. * After the code complete milestone, no entirely new product source code will be added to this release. * All source code commit log messages must refer to a specific issue ID, after the feature complete milestone. How will this plan be updated? This project plan will be updated as needed throughout the project. It will be placed under version control and instructions for accessing it will be on the project website. Any change to the plan will cause an automatic notification to be sent to a project mailing list. Work Breakdown Structure and Estimates TODO: List tasks that will be needed for this project. Keep dividing tasks into subtasks until you feel that you have enough detail to expose risks and make reasonable estimates in ideal engineering hours. TIP: Label each step uniquely to show its position in the WBS, e.g., Step 1.1.4.A. Use numbers for steps that you intend to do in sequence, and use letters for steps that you intend to do in parallel. E.g., Step 1.1 comes before Steps 1.2.A and 1.2.B, but those two steps may be done in parallel, and Step 1.3 will be done after all 1.2.* steps have been finished. Don't worry about renumbering if you delete a step. Step Description Estimate 1. Preparation 1.1. Developer training 30h 2. Inception 2.1. Requirements gathering 30h 2.2. Requirements specification 20h 2.3. Requirements validation 10h 3. Elaboration 3.1. High-level design 5h 3.2. Low-level design (break down by component) 3.2.A. Object design 10h 3.2.B. User interface design 10h 3.2.C. Database design 3h 3.3. Design review and evaluation 5h 4. Construction 4.1.A. System implementation 4.1.A.1. Implement COMPONENT-NAME 1 25h 4.1.A.2. Implement COMPONENT-NAME 2 25h 4.1.A.3. Implement COMPONENT-NAME 3 25h 4.1.A.4. Implement COMPONENT-NAME 4 25h 4.1.A.5. Integrate Components (mostly done during component implementation) 5h 4.1.B. Technical documentation (break down by component) 10h 4.1.C. User documentation (break down by component) 10h 4.1.D. Testing 4.1.D.1. Test planning 10h 4.1.D.2. Test code implementation (break down by component) 30h 4.1.D.3. Test execution 10h 4.2. Implementation review and evaluation 15h 5. Transition 5.A. Release packaging 3h 5.B. Documentation for other groups 3h 6. Reflection 6.1. Postmortem report 10h Total 329 hours Deliverables in this Release TODO: List project deliverables in detail, with delivery dates. Deliverable Name Description Delivery Date Deliverable Name Description Delivery Date Deliverable Name Description Delivery Date Deliverable Name Description Description Description Description Description Description Description Description Delivery Date Deliverable Name Description Delivery Date Schedule for this Release TODO: Make the rows in this table match the steps in your WBS above. If you have a large number of detailed steps, you can skip the most detailed ones. The columns of the table represent weeks of calendar time. For each cell in the table, enter the number of hours ideal engineering time that the team will spend on that task that week. Total your hours across and down. TIP: These hours should total to the same as the total of the hours listed in your resource needs document. And, the hours for each type of effort resources needed should correspond to the sum for each type of task. Task \ Week W-01 W-02 W-03 W-04 W-05 W-06 W-07 W-08 W-09 W-10 W-11 W-12 Task Total 1. 00 00 00 00 00 00 00 00 00 00 00 00 00 2. 00 00 00 00 00 00 00 00 00 00 00 00 00 3. 00 00 00 00 00 00 00 00 00 00 00 00 00 4.1.A. 00 00 00 00 00 00 00 00 00 00 00 00 00 4.1.B. 00 00 00 00 00 00 00 00 00 00 00 00 00 4.1.C. 00 00 00 00 00 00 00 00 00 00 00 00 00 4.1.D. 00 00 00 00 00 00 00 00 00 00 00 00 00 4.2. 00 00 00 00 00 00 00 00 00 00 00 00 00 5. 00 00 00 00 00 00 00 00 00 00 00 00 00 6. 00 00 00 00 00 00 00 00 00 00 00 00 00 Weekly Totals 00 00 00 00 00 00 00 00 00 00 00 00 00 Risk Management TODO: List and rank the major risks of this project, and what you plan to do to mitigate each risk. If you don't plan to do anything to mitigate the risk, state that. Use the risk list below, or the risks worksheet. Please see the risks worksheet. The main risks of this project are: 1. There is a potential conflict between the goals of a high-quality appearance and one that is completely customizable. We can only succeed if players find the web site appealing, and game vendors can customize it with no more effort than would be needed to build a static website. We already have a design in mind that will address this risk and we will review it with a web site designer who worked for a game vendor site. 2. There are significant technical difficulties in building a web site and web application. This will be a risk because one person on our team has much experience with the relevant tools and technologies. Although the others will learn, we will certainly make some mistakes and suboptimal choices. We will address this risk by scoping the project such that we have enough time to train and to review the design and implementation. 3. The schedule for this project is very short. We will manage this by planning a conservatively scoped functional core and series of functional enhancements that can be individually slipped to later releases if needed. 4. The performance of the system will be significantly impacted by the decisions made during the database design task. None of our current team members has experience with database optimization. To address this, we will arrange a review meeting with an experienced DBA or hire a consultant from the database vendor. 5. We could be underestimating known tasks. HOW TO AVOID/MITIGATE? 6. We could be underestimating the impact of unknown tasks. HOW TO AVOID/MITIGATE? 7. We could be underestimating the dependencies between tasks. HOW TO AVOID/MITIGATE? 8. We could have misunderstood the customer's requirements. HOW TO AVOID/MITIGATE? 9. The customer could change the requirements. HOW TO AVOID/MITIGATE? 10. We could face major difficulties with the technology chosen for this project. HOW TO AVOID/MITIGATE? 11. We could have low quality that demands significant rework. HOW TO AVOID/MITIGATE? 12. We could incorrectly assess our progress until it is too late to react. HOW TO AVOID/MITIGATE? 13. We could lose resources. E.g., team members could get sick, spend time on other projects, or quit. HOW TO AVOID/MITIGATE? 14. There may be a mis-alignment of stakeholder goals or expectations. HOW TO AVOID/MITIGATE? Project Planning Dependencies Does this project conflict or compete for resources with any other project? No, this is the only project that we are working on. Yes, and we have determined how many hours each person can actually dedicate to this project. Are the same human or machine resources allocated to maintenance of past versions and/or planning of future versions during this release time period? No, this is the first release and we will not plan the next release. Yes, we predict that team members will spend an average of 20% of their time maintaining previous releases and planning future releases during this release time frame. Some weeks may be higher if an urgent patch to a previous release is needed. Does this project depend on the success of any other project? No, this project stands alone. Yes, project P1 must provide library L, and project P2 must prove the usability of feature F, and.... Does any other project depend on this project? No, project is not producing any components that will be used in other current projects. Yes, we must produce library L for our project and support users of L in projects P1 and P2. Are there any other important dependencies that will affect this project? No, everything is covered above. Yes. DETAILS.... TODO: Check for words of wisdom and discuss ways to improve this template. Or, eva Project Information
Project: PROJECTNAME
Project Time-frame: STARTDATE - ENDDATE
Attached worksheets:
Plan > Resource needs
Related Documents:
Project proposal > Target audience and benefits
Software development methodology
Glossary
Process impact: This plan will be used to evaluate and manage the project. Key assumptions that affect the plan should be documented here. The project plan should be updated throughout the life-time of the project.
TODO: Fill in the information above and below. Add or remove rows as needed. Use the worksheet to help identify and scope resource needs.
Summary of Project

ONE OR TWO SENTENCES HERE. For more information see the Project proposal.

IF YOU PLAN TO ORGANIZE YOUR WORK ACCORDING TO A ROUGH BREAKDOWN OF SOFTWARE COMPONENTS, BRIEFLY DESCRIBE THOSE COMPONENTS HERE. FOUR TO TEN BULLETS.
Summary of Methodology

What general development approach will be used?
THREE TO FIVE SENTENCES OR BULLETS HERE. COVER GENERAL APPROACH, IMPORTANT ASSUMPTIONS, KEY PRACTICES, AND PROJECT COORDINATION CONTROLS. For more information see the Software Development Methodology.
How will the project team be organized?
The development team will consist of …
The change control board will consist of …
What development and collaboration tools will be use?
We plan to use the following tools extensively through out the project:

* Project website
* Project mailing lists
* Issue tracking system
* Version control system
* Automated build system
* Automated unit test system

How will changes be controlled?

* Requests for requirements changes will be tracked in the issue tracker
* The change control board (CCB) will review requested changes and authorize work on them as appropriate
* After the feature complete milestone, no new features will be added to this release.
* After the code complete milestone, no entirely new product source code will be added to this release.
* All source code commit log messages must refer to a specific issue ID, after the feature complete milestone.

How will this plan be updated?
This project plan will be updated as needed throughout the project. It will be placed under version control and instructions for accessing it will be on the project website. Any change to the plan will cause an automatic notification to be sent to a project mailing list.

Work Breakdown Structure and Estimates
TODO: List tasks that will be needed for this project. Keep dividing tasks into subtasks until you feel that you have enough detail to expose risks and make reasonable estimates in ideal engineering hours.
TIP: Label each step uniquely to show its position in the WBS, e.g., Step 1.1.4.A. Use numbers for steps that you intend to do in sequence, and use letters for steps that you intend to do in parallel. E.g., Step 1.1 comes before Steps 1.2.A and 1.2.B, but those two steps may be done in parallel, and Step 1.3 will be done after all 1.2.* steps have been finished. Don’t worry about renumbering if you delete a step.
Step Description Estimate
1. Preparation
1.1. Developer training 30h
2. Inception
2.1. Requirements gathering 30h
2.2. Requirements specification 20h
2.3. Requirements validation 10h
3. Elaboration
3.1. High-level design 5h
3.2. Low-level design (break down by component)
3.2.A. Object design 10h
3.2.B. User interface design 10h
3.2.C. Database design 3h
3.3. Design review and evaluation 5h
4. Construction
4.1.A. System implementation
4.1.A.1. Implement COMPONENT-NAME 1 25h
4.1.A.2. Implement COMPONENT-NAME 2 25h
4.1.A.3. Implement COMPONENT-NAME 3 25h
4.1.A.4. Implement COMPONENT-NAME 4 25h
4.1.A.5.
Integrate Components
(mostly done during component implementation)
5h
4.1.B. Technical documentation (break down by component) 10h
4.1.C. User documentation (break down by component) 10h
4.1.D. Testing
4.1.D.1. Test planning 10h
4.1.D.2. Test code implementation (break down by component) 30h
4.1.D.3. Test execution 10h
4.2. Implementation review and evaluation 15h
5. Transition
5.A. Release packaging 3h
5.B. Documentation for other groups 3h
6. Reflection
6.1. Postmortem report 10h
Total 329 hours
Deliverables in this Release
TODO: List project deliverables in detail, with delivery dates.
Deliverable Name Description Delivery Date
Deliverable Name Description Delivery Date
Deliverable Name Description Delivery Date
Deliverable Name Description Description Description Description Description Description Description Description Delivery Date
Deliverable Name Description Delivery Date
Schedule for this Release
TODO: Make the rows in this table match the steps in your WBS above. If you have a large number of detailed steps, you can skip the most detailed ones. The columns of the table represent weeks of calendar time. For each cell in the table, enter the number of hours ideal engineering time that the team will spend on that task that week. Total your hours across and down.
TIP: These hours should total to the same as the total of the hours listed in your resource needs document. And, the hours for each type of effort resources needed should correspond to the sum for each type of task.
Task \ Week W-01 W-02 W-03 W-04 W-05 W-06 W-07 W-08 W-09 W-10 W-11 W-12 Task Total
1. 00 00 00 00 00 00 00 00 00 00 00 00 00
2. 00 00 00 00 00 00 00 00 00 00 00 00 00
3. 00 00 00 00 00 00 00 00 00 00 00 00 00
4.1.A. 00 00 00 00 00 00 00 00 00 00 00 00 00
4.1.B. 00 00 00 00 00 00 00 00 00 00 00 00 00
4.1.C. 00 00 00 00 00 00 00 00 00 00 00 00 00
4.1.D. 00 00 00 00 00 00 00 00 00 00 00 00 00
4.2. 00 00 00 00 00 00 00 00 00 00 00 00 00
5. 00 00 00 00 00 00 00 00 00 00 00 00 00
6. 00 00 00 00 00 00 00 00 00 00 00 00 00
Weekly Totals 00 00 00 00 00 00 00 00 00 00 00 00 00
Risk Management
TODO: List and rank the major risks of this project, and what you plan to do to mitigate each risk. If you don’t plan to do anything to mitigate the risk, state that. Use the risk list below, or the risks worksheet.

Please see the risks worksheet.

The main risks of this project are:

1. There is a potential conflict between the goals of a high-quality appearance and one that is completely customizable. We can only succeed if players find the web site appealing, and game vendors can customize it with no more effort than would be needed to build a static website. We already have a design in mind that will address this risk and we will review it with a web site designer who worked for a game vendor site.
2. There are significant technical difficulties in building a web site and web application. This will be a risk because one person on our team has much experience with the relevant tools and technologies. Although the others will learn, we will certainly make some mistakes and suboptimal choices. We will address this risk by scoping the project such that we have enough time to train and to review the design and implementation.
3. The schedule for this project is very short. We will manage this by planning a conservatively scoped functional core and series of functional enhancements that can be individually slipped to later releases if needed.
4. The performance of the system will be significantly impacted by the decisions made during the database design task. None of our current team members has experience with database optimization. To address this, we will arrange a review meeting with an experienced DBA or hire a consultant from the database vendor.
5. We could be underestimating known tasks. HOW TO AVOID/MITIGATE?
6. We could be underestimating the impact of unknown tasks. HOW TO AVOID/MITIGATE?
7. We could be underestimating the dependencies between tasks. HOW TO AVOID/MITIGATE?
8. We could have misunderstood the customer’s requirements. HOW TO AVOID/MITIGATE?
9. The customer could change the requirements. HOW TO AVOID/MITIGATE?
10. We could face major difficulties with the technology chosen for this project. HOW TO AVOID/MITIGATE?
11. We could have low quality that demands significant rework. HOW TO AVOID/MITIGATE?
12. We could incorrectly assess our progress until it is too late to react. HOW TO AVOID/MITIGATE?
13. We could lose resources. E.g., team members could get sick, spend time on other projects, or quit. HOW TO AVOID/MITIGATE?
14. There may be a mis-alignment of stakeholder goals or expectations. HOW TO AVOID/MITIGATE?

Project Planning Dependencies

Does this project conflict or compete for resources with any other project?
No, this is the only project that we are working on.
Yes, and we have determined how many hours each person can actually dedicate to this project.
Are the same human or machine resources allocated to maintenance of past versions and/or planning of future versions during this release time period?
No, this is the first release and we will not plan the next release.
Yes, we predict that team members will spend an average of 20% of their time maintaining previous releases and planning future releases during this release time frame. Some weeks may be higher if an urgent patch to a previous release is needed.
Does this project depend on the success of any other project?
No, this project stands alone.
Yes, project P1 must provide library L, and project P2 must prove the usability of feature F, and….
Does any other project depend on this project?
No, project is not producing any components that will be used in other current projects.
Yes, we must produce library L for our project and support users of L in projects P1 and P2.
Are there any other important dependencies that will affect this project?
No, everything is covered above.
Yes. DETAILS….

TODO: Check for words of wisdom and discuss ways to improve this template. Or, eva

]]> By: Mr. Patric Masiemo- Kenya http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-24247 Mr. Patric Masiemo- Kenya Sun, 05 Sep 2010 10:38:28 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-24247 It's one of the important tool used by a number of organizations to mobilize the resources. So you're doing good job to empower groups, individuals and organizations to manage their own projects. It’s one of the important tool used by a number of organizations to mobilize the resources. So you’re doing good job to empower groups, individuals and organizations to manage their own projects.

]]> By: Musisi Rajab http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-24014 Musisi Rajab Sat, 28 Aug 2010 09:09:48 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-24014 I think this is very important for all those interested in aquaring knowledge. i only thank all those who were behind this because it a way of sharing, hence contributes to development. I think this is very important for all those interested in aquaring knowledge. i only thank all those who were behind this because it a way of sharing, hence contributes to development.

]]> By: Wilfred Browne http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-22978 Wilfred Browne Thu, 22 Jul 2010 15:25:12 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-22978 Hi friends i want know how to write project proposal. Thank for your concern. Hi friends i want know how to write project proposal.
Thank for your concern.

]]> By: Peter La. Julian http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-22593 Peter La. Julian Wed, 07 Jul 2010 21:12:24 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-22593 For those who have not made a project proposal, a set-by-step process on how to make one would be more practical. For example, there is a dearth of Ilocano (one of the Philippine"s ethno-linguistic groups) magazines in the country, especially in Northern Luzon. There is a great number of writers in the language.One of the biggest dailies can publish the magazine. How will the writers make the project proposal to the sail daily newspaper? For those who have not made a project proposal, a set-by-step process on how to make one would be more practical. For example, there is a dearth of Ilocano (one of the Philippine”s ethno-linguistic groups) magazines in the country, especially in Northern Luzon. There is a great number of writers in the language.One of the biggest dailies can publish the magazine. How will the writers make the project proposal to the sail daily newspaper?

]]> By: Ronald Wakere http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-12535 Ronald Wakere Thu, 26 Nov 2009 05:36:19 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-12535 I would like a sample copy of your project proposal report. thank you I would like a sample copy of your project proposal report.
thank you

]]> By: Choloply Q. Toe http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-8497 Choloply Q. Toe Fri, 21 Aug 2009 14:41:14 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-8497 Thanks for the enlighten my elite on projct proposal. I will apperciate were you could help with a tutorial. I wish to presuade my master programme in project management. Thanks for the enlighten my elite on projct proposal. I will apperciate were you could help with a tutorial. I wish to presuade my master programme in project management.

]]> By: Charles http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-7984 Charles Wed, 05 Aug 2009 15:50:11 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-7984 It is a good approach and it would be better if a sample was given to make it easy to understand. Thanks for good work. It is a good approach and it would be better if a sample was given to make it easy to understand.
Thanks for good work.

]]> By: MARIA DOLORES C. YABUNAN http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-7218 MARIA DOLORES C. YABUNAN Thu, 16 Jul 2009 01:57:14 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-7218 It's good to find guides on making a project proposals on line. It surely help me a lot. Thanks. It’s good to find guides on making a project proposals on line. It surely help me a lot. Thanks.

]]> By: Ajayi, Adeyemi http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-728 Ajayi, Adeyemi Wed, 29 Apr 2009 11:44:28 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-728 This is a well articulate and all embracing project proposal format. you have really done perfectly well. This is a well articulate and all embracing project proposal format. you have really done perfectly well.

]]> By: ZUBAIDA FUTA http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-733 ZUBAIDA FUTA Tue, 07 Apr 2009 13:07:40 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-733 This is only an introduction. Can you tell me all abouse project proposal from planning stage to evaluation stage. This is only an introduction. Can you tell me all abouse project proposal from planning stage to evaluation stage.

]]> By: PM Hut http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-732 PM Hut Thu, 19 Mar 2009 15:12:35 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-732 Hi Falak, here's a <a href='http://www.pmhut.com/wp-content/uploads/2008/01/concept_proposal.pdf' rel="nofollow">project proposal template</a> (it's actually labeled as concept proposal). Hi Falak,

here’s a project proposal template (it’s actually labeled as concept proposal).

]]> By: falak naz http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-731 falak naz Thu, 19 Mar 2009 11:45:23 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-731 though this site gives us help about how to write a project proposal but i (think as a student)you should give a sample of a project proposal online so that the new comers on this site can properly take an idea of proposal thanks though this site gives us help about how to write a project proposal but i (think as a student)you should give a sample of a project proposal online so that the new comers on this site can properly take an idea of proposal
thanks

]]> By: How to Write a Project Charter - Part 1 - PM Hut http://www.pmhut.com/how-to-write-a-project-proposal/comment-page-1#comment-730 How to Write a Project Charter - Part 1 - PM Hut Fri, 06 Feb 2009 23:17:12 +0000 http://www.pmhut.com/how-to-write-a-project-proposal#comment-730 [...] but healthy process for a group of key stakeholders in a corporate environment. For that reason, a project proposal should be written and approved before the project charter is [...] [...] but healthy process for a group of key stakeholders in a corporate environment. For that reason, a project proposal should be written and approved before the project charter is [...]

]]>