Planning & Execution
Table of Contents
Sample categories are listed below, but feel free to change or add nodes to better correspond to your project and your Guide’s expectations. To save time and effort, add links to documents within your EDGE file repository whenever possible.
Customer NeedsExcel version: Customer_Needs.xls
- USB Charger: the stirling generator must output its power through a USB port.
- Stirling Engine: the generator must be powered by an engine utilizing the Stirling cycle.
- Solar Power: the stirling engine must obtain its energy from the sun
- Self Start:stirling generator often need a little push to get moving. This engine must get this little push autonomously.
- Low Maintenance: the stirling generator should be able to operate an extended period of time without any need for a person to check and ensure it is properly operating.
- Inexpensive: this stirling generator must fit within the project budget.
- Light Weight: a single person must be able to easily move, mount, and dismount this stirling engine/generator.
- Safe: this stirling generator should not cause any damage to people when operated on or to buildings/structures when in use.
- Power: the stirling generator must provide at least 10 watts of power when operating.
- Voltage: the stirling generator must provide a nominal voltage of 5 volts when operating.
- Price: the stirling generator must cost less then $500.
- Weight: the stirling generator must weigh less then 20 pounds.
- Mean Time Between Failures: the stirling generator must operate for a minimum of 1 year before having a failure and needing to be maintenance.
- Weatherproof: the stirling generator must be able to withstand all weather conditions.
Team Norms & Values (Code of Ethics)
- Behavior Expectations: Each team member is expected to cooperate and be willing to compromise with other members. Professionalism is to be maintained at all times.
- Work Distribution: Project deliverable's and action items (past and new) will be reviewed at the beginning of every meeting and new one's assigned and agreed to at the end of each meeting. Each team member will be required to say whether they feel they are doing too much, not enough, or the correct amount of work.
- Team Roles: Each member's roles and responsibilities will be decided based upon their strengths and weaknesses as decided by consensus.
- Honor Strengths: Members strengths will be honored as much as possible when determining their roles and responsibilities, within the bounds of the project.
- Guide Interaction: The guide will be invited to participate in a weekly meeting project meeting, and will be contacted as needed through email and phone.
- Group Interaction: The group members will communicate mainly through the weekly meetings, and email as needed.
- Decision Making: Decisions for this group will be made on a consensus basis at team meetings. No major decisions will be made until everyone in the group has had a chance to state their opinion.
- Expectations for Integrity and Responsibility: Members will be expected to complete their assigned work by the dates agreed to, as well as participate and put in an honest effort in the project design through weekly meetings and email.
- Manage Conflict: The group will expect to be alerted to any task or assignment that cannot be completed by the expected date by the assignee before said date as soon as this is realized. A redistribution of the task to more members, more group brainstorming, or perhaps additional time can then be granted for the task. This will help mitigate any risk as it arises and not at the last possible minute. Conflict between individuals will be resolved as a group if possible, elevating to the guide if adequate resolution cannot be met.
- Background Research
Project Plans & Schedules
WBS, 1-page project summary, Gantt charts, etc. MSD I & II
Communication Methods and SkillsMost communication via email, text or call via phone where necessary. Phone numbers have been exchanged between all team members.
|Phil Glasseremail@example.com||Electronics design, control systems (classical and state space), embedded systems|
|William Tierneyfirstname.lastname@example.org||Aerospace, controls and vibration|
|Bryan Abbottemail@example.com||Welding, piston seals|
|Mike Sciontifirstname.lastname@example.org||Finite element analysis, stress analysis, linkages|