MANAGEMENT

The management details for the project are outlined below. These may evolve as the semester progresses.

34.3.1 Timeline - Tentative

[an error occurred while processing this directive]

Sept 12 - Teams assigned

Sept 12 - Teams matched with EGR 101 students

Sept 14 - EGR 345 Teams visit EGR 101 lab - EC616 (6pm) to formalize contracts

Sept 16 - Contract submitted

Oct 4 - Preliminary design concept submitted with specifications

materials list estimate

budget estimate

Gantt charts

Oct 13 - Design concept approved

Oct 24 - Proposal submitted

detailed drawings (CAD)

materials list

budget

calculations/simulations

Oct 29 - Proposals approved, 345/101 building begins

Nov 12 - First test

Nov 19 - Second test

Nov 20 - First draft of report posted to the web used to determine the score for competition

Nov 25 - Competition and judging

Dec 4 - Final report draft posted to the web

34.3.2 Teams

[an error occurred while processing this directive]

The teams are composed of up to 4 students from EGR 345 and one student from EGR 101. The EGR 345 teams are grouped using the skills survey attached in the appendices.

 

Teams are expected to divided tasks for members to work in parallel. It is also expected that team members will review the work of others to ensure accuracy and completeness. This is particularly true of calculations, materials lists drawings and budgets.

 

All team members are expected to work in a professional manner. The general rules of conduct in a team are,

- treat others as you want to be treated

- communicate expectations and problems clearly

- be polite and accommodating

- when problems arise, help to solve them, even if they are not your fault. Don’t lay the blame for problems on others.

 

Personal conflicts must be resolved by team members in a professional manner. The performance of the team will be assessed using peer evaluations on a regular basis and may impact individual grades. In the case of non-participation the penalty may be up to 100% of the project grade.

 

In the event that team members cannot resolve differences with a team member, the team may ’fire’ the team member by a vote (it must be unanimous, except for the member in question). In this case the ’fired’ student is responsible for finding another team that will accept (or ’hire’) them. In the event they cannot find another team to join, they will be expected to perform all of the work themself. The firing mechanism is intended to deal with individuals who ’harm’ the progress of the team, not for non-participants.

[an error occurred while processing this directive]