{Project Name - Sub-Project Name}

Project Proposal

{Draft Number}

Italicized comments within this template should be removed from the final document

INDEX

Contact & Distribution
Revision History
Executive Summary
Problem or Opportunity
Proposal
Project Scope
Cost/Benefit
Project Definition
Problem or Opportunity
Business Objectives
Project Scope
Preliminary Requirements
Assumptions
Constraints
Risk Factors
Issues & Concerns
Project Proposal
Proposal
Alternatives
Cost/Benefit Analysis
Roles & Responsibilities
Preliminary Project Schedule
Appendix A - Project Initiation Request
Appendix B - Supporting Documents
Appendix C - Glossary

CONTACT & DISTRIBUTION

REVISION HISTORY

Date of Revision Revised by Description of Revision Affected Modules

EXECUTIVE SUMMARY

The intent of this summary is to give a very high level overview of the project, directed to upper management, financial backers, etc.  These summarize information that is expounded upon in detail later in the document.

PROJECT DEFINITION

PROJECT PROPOSAL

Proposal

Detail the proposal that you have selected as your primary choice.  Remember, you've already selected this as the best of the alternatives, so present it in that light.  Also, you're not designing it now; that's next phase.  So don't get bogged down in details.

Alternatives

  1. For each of the alternatives you list, provide justification for its rejection.  Some alternatives may be rejected outright; others are possibly fallback positions.  Make sure the difference is clear. Options considered should always include:
  2. Purchase packaged application.  Do you NEED to do this?
  3. Partner with someone else to provide a solution.  It may be that another company has a solution that is ALMOST what you need; and that cantracted changes may be more cost-effective than in-house development.
  4. Doing nothing is ALWAYS an alternative.

Cost/Benefit Analysis

  1. List all known costs (for example, Systems, Legal, Business Unit, Marketing, Administrative).
  2. List benefits resulting from the successful completion of this project.  Some benefits may be stated as "intuition".
  3. Spell out the "bottom line" financially (Benefits - Cost).
  4. List alternative Cost/Benefit analyses for alternatives (such as "what do we lose if we DON'T do the project")

Roles & Responsibilities

  1. Names aren't necessary here, but positions and responsibilities ARE.
  2. Show an organization chart, if appropriate, and state clearly who has responsibility for managing the project and coordinating effort.

Preliminary Project Schedule

I recommend linking to an external schedule.  This should be kept in revision control.

APPENDIX A - PROJECT  INITIATION REQUEST

Reference via hypertext link.

APPENDIX B - SUPPORTING DOCUMENTS

Reference via hypertext link.

APPENDIX C - GLOSSARY

Reference via hypertext link.