Engineering Projects/Igloo/Howard Community College/Fall2012/p1-502-rmwh
Please delete everything in italics after filling it out.
Project documentation focuses on how the team organized itself to tackle the unknown. This is a creative process. The details learned should be captured in tutorials. Project documentation should focus on how the team organized itself to step out into the unknown. Failure is common. The single most effective way to increase engineering respect is to document failures in a creative way that stimulates, inspires and helps others continue the project. Projects are never done. There are always loose ends. There are always decisions that might have been made more clearly. There are always other alternatives that might have been considered. None of this stuff appears in a tutorial. It does appear in the team documentation.
Electronic Sections Expected edit
Problem Statement edit
What is the final, negotiated problem statement?
Team Members edit
Put each team members name here with links to their user pages here. Real names do not have to be used.
Summary edit
Put an overall, short one paragraph summary here.
Poster edit
Put a graphic in wikimedia, include the graphic here or link to it here. The graphic should be suitable for creating a traditional project poster.
Story edit
Tell a detailed story of the project. Describe how split up, what the obstacles were, what testing was done, what informal decisions were made, what assumptions were made, what the results were.
Decision List edit
List all formal decisions made with links to their documentation such as a decision tree or decision matrix.
Material List edit
- 1. List materials used, quantity, size, cost.
- 2. Describe what needs to be purchased in the future to continue working on this project.
Software List edit
You installed different software packages or used already installed software. Describ the programs here.
Time edit
Put one number here. Hours. Total hours that everyone worked on the project. Do not estimate. Do not talk about it. ADD.
Tutorials edit
All projects create new tutorials of technical details future participants are going to want to know. They are going to be separate pages that are linked to here.
Next Steps edit
List specific details, advice, describe the current problems that the next team faces associated with the project here.