Decent Proposal | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Opinion
Executive
Resources
|
Home > Departments > Methods & Means
Project managers must get into the habit of talking about projects in business terms. It can help to reduce communication problems, and smooth the way for customers and teams to work more effectively together. Project proposals are a real good place to start, even if it means writing them retrospectively after the work has been approved.
This is an excerpt from Chapter 2 of The Principles of Project Management (SitePoint Pty. Ltd.; March 2008).
Project proposals are simple, short (usually single-page) documents that outline the potential project, provide brief background information, identify the value of undertaking the project, and give a very rough estimate of the resources (budget, people, time) that would be required to deliver the project. (Project proposals are sometimes called project request documents (PRDs) or project charters, though the latter indicates a little more finality and is more like the project initiation document.)
Ideally, a project proposal is collected for each of the possible projects, and from this pool, the projects that are determined to have the potential to deliver the greatest benefit to the organization are chosen.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement