Project Proposal Form with guidelines

From Bob's Basement

[edit] Project Proposal Form With Guidelines

• By Bob_Plonker & BOfH
• Monday 9th March 2009

1. Project Summary:

Good for recruiting group members to your project.

2. Goal:

What are you trying to do? Be concise.

3. Description:

Detailed description of the entire project. More is better.

4. Scope:

What are the project boundaries. What will it not do. This prevents feature creep.

5. Tasks:

Breakdown into byte size elements that can be tackled one at a time. The tasks is the most important part of the project proposal. If your project cannot be broken down successfully then it is unlikely to succeed.

6. Task Dependencies:

What are the dependencies of each of the above tasks. What resources does each task require? Do any of your tasks require skills/tools/any resource that maybe in short supply. This will reduce the chances of a Bobs Basement resource bottleneck with another project. It will also enable us to schedule your project into physical meets more easily.

7. Milestones:

These are points where the project actually achieves something that works. It allows us to take things a step at a time, first delivering a working bare minimum and adding features on. eg: Build an autonomous car with weapons system:

Milestone 1: Build a remote control car Milestone 2: Add autonomous guidance Milestone 3: Add the weapons system

8. Technical Challenges:

What particular skills do you lack that the project requires? What do you not know how to do NOW. Don't make assumptions that you will be able to learn the required skills. Projects require accurately matching project members with tasks by dependent skills.

9. Project Completion Date:

Perhaps for a particular event. We are aware that all project completion dates are resource dependant. We won't hold you to your proposed project completion date so don't panic.

10. Project Cost:

List all components, consumables and equipment costs required for your project proposal.