Project Proposal

A project proposal/plan shall be required for every project assigned to members of TWiCE. The project plan lists and describes all essential and technical requirements for the effort to be performed, including standards to be used to determine whether the requirements have been met.

The purpose of the project proposal is to document the required software application's features and capabilities, making the schedule and cost estimates more reliable.

[Specify the purpose of this Project Proposal; in particular, what kind of service is being provided and for whom. This section should function as an abstract for the document. It should help the reader decide whether to read the rest of the document. For example, a client should get enough information from this section to decide if this project is attractive and whether to pursue it.]

[This subsection should describe what the rest of the Project Proposal contains and explain how the document is organized.]

Project Name: <Insert Project Name>

Client Information: Include as many clients' names as are associated with the project in any capacity.

Client Name:                          <Insert Client Names>
Client Address:                      <Insert Client Address1>
                        <Insert Client Address2>
Client Phone:                         <Insert Client Phone>
Client Fax:                           <Insert Client Fax>
Client Email:                          <Insert Client Email>

The Women In Computer Engineering is an industry-facing organization within the Dept. of Computer Science & Engineering (CS&E) and the College of Engineering (C.O.E.) at The Ohio State University (O.S.U.).

Students from the Ohio State University and members of TWiCE. will be extensively involved in this effort. Student learning will be an explicit and key part of this effort. A set of learning outcomes for the students will be explicitly identified along with each deliverable for the project. The time and effort required for the learning is to be the responsibility of the student and TWiCE. The client is not expected to provide subsidization for such training and development.

At all times, the project will be professionally managed, in accordance with industry best practices. A comprehensive project plan will be created and maintained, deliverables will have clear outcomes and deadlines mutually identified and then adhered to.

A project of this complexity requires the close involvement of the client. At least one person in the client's organization will be explicitly identified and necessarily and closely engaged for each deliverable. In essence, this resource will be at least equal participants in each phase of this effort. Thus, the client will feel ownership of the project, commit to it, and maintain it as a living and key Information Technology asset.

Project Lead                       <Insert Project Lead>

[Provide information about the experience and qualifications of the Project Lead]

Lead Name:                       <Insert Lead Names>
Lead Address:                      <Insert Lead Address1>
                       <Insert Lead Address2>
Lead Phone:                         <Insert Lead Phone>
Lead Fax:                           <Insert Lead Fax>
Lead Email:                          <Insert Lead Email>

Supporting Members:           <Insert Names and short qualification statements>

[A brief description of the scope of this Project Proposal; what other Project(s) it is associated with, and anything else that is affected or influenced by this document.]

[Summarize the current system and provide some motivation for a new system at this time. The main audience for this section would be analysts, designers and implementers who join the project later. If this project is related to a new system, describe what business need this system will solve. Compare the proposed new system to other competing systems.]

What the new system will not be responsible for (drawn from responsibilities that might be conceivably within the scope of the system

1. Task Name:
Priority: [high | medium | low]
Description - a positive statement of what work will be done
Rationale - relationship to the overall project.
1.1 Any SubTask Names, Description

2. Task Name:
Priority: [high | medium | low]
Description - a positive statement of what work will be done
Rationale - relationship to the overall project.
2.1 Any SubTask Names, Description

[etc.]

[This section is typically organized chronologically, but alternative organization methods may also be appropriate. For example, you may choose to organize by user, or by function. ]

Project Proposal Form