Planning & Execution
Table of Contents
Intellectual Property ConsiderationsThe Overcomer team will continue working upon the Patent filed by Joe Kabes (US 2016/0271478 A1).
|Cesar Borges||Biomedical Engineering||Systems Engineer/EDGE Coordinatoremail@example.com|
|Kalie Lazarou||Industrial & Systems Engineering||Project Managerfirstname.lastname@example.org|
|Rachel Mahoney||Biomedical Engineering||Systems Engineer/Financial Coordinatoremail@example.com|
|Michael Martin||Mechanical Engineering||Design Engineerfirstname.lastname@example.org|
|Karn Mishra||Industrial & Systems Engineering||Systems Engineer/Data Analystemail@example.com|
A full listing of team’s skills and experience can be found here.
Team Values and Norms
|Values||Punctuality||Thorough||Accurate||Professional & Ethical||Collaborative||Committed|
|Meets||Be on time for meetings and class, if you have a planned absence make the team aware at least 48 hours in advance. If something comes up after that let the team know ASAP.||Follows general structure determined by team, work is concise and clear to all other team members, all work is uploaded/organized on google drive.||The work completed by the member contains a few errors that must be corrected. The basic approach to problem solving is good, and the errors are relatively minor and could be readily corrected through normal peer review and checking. The work was corrected through consultation with the team members or faculty guide.||Behaves responsibly in all situations related to project work and respects all individual team members. Team member does not demean other team members’ work.||The team member is completing work that is not counterproductive and achieves the goals of the collective team.||The team member is carrying their fair share of the workload and is dedicated to goals set by the team as a collective unit.|
|Needs Improvement||Is consistently late or skipping out early to/from class or meetings, for example: comes late with coffee, without notifying team.||Follows parts of structure, does not explain work completed fully, all work is uploaded/organized on google drive.||The work completed by the member contains many errors that must be corrected. While the basic approach to problem solving may be ok, the actual work completed needs to be largely re-done in order to be useful to the team. Some things were not done by the team member, that should have been obvious to complete.||Behaves responsibly in most situations related to project work and respects all individual team members. Team member does not demean other team members’ work.||Team member completes work that is acting against others’ work or is not meeting the goals of the collective team||Team member is not interested in the work, doesn’t take on as many tasks from the project.|
|Unsatisfactory||Consistently misses Friday meetings/ class without notifying team.||Does not follow structure determined by the team, work is not uploaded to google drive, for example, final edition of work completed is chicken scratch in your own notebook.||The work completed by the member is completely inaccurate and must be completely reworked. Basic approach was incorrect, and not agreed upon by the team. No communication from team member about their struggles to obtain accurate work.||Does not behave responsibly in situations related to project work and does not always respects all individual team members. Team member demeans other team members’ work.||Team member is doing work unrelated to the goals of the collective team||Team member is completely uninterested in anything related to project and becomes a burden to the productivity of the team.|
A live document of our team's values and norms can be found here.
Project Plans & Schedules
Risk Assessment and Growth Curves
A live version of risk assessment can be found here
Meeting Minutes, Notes, & ActionsMeeting minutes to be added soon.
- Phase I: Problem Definition Peer Reviews
- Phase II: Systems Design Peer Reviews
- Phase III: Preliminary Design Peer Reviews
- Phase IV: Detailed Design Peer Reviews
- Customer point of contact: Joe Kabes (Overcomer)
- Establish preferred method of communication: Email, Text, or Call
- Establish expected frequency of communication: Weekly or as needed
- Determine customer availability for each of the 5 reviews: Monday's or Wednesday's beginning at 4 PM
- Identify a team member to handle customer
communication: Kalie Lazarou (Project Manager)
- Establish team expectations for cc on customer emails: Entire team is cc'ed when needed
- Set expectations for how/when pre-read documentation will be shared with customer: At least 24 hours before design review
- Establish expectations for within-team communication
- Establish preferred method of communication: Slack, Email, and text when needed.
- Establish expectations for how/when to include guide in communication
- Establish team expectations for cc on within-team messages