P20414: Indoor Dry Toilet Base
/public/

Planning & Execution

Table of Contents

Intellectual Property Considerations

All work done within the group will be public domain.

Team Setup

Purpose

  1. Facilitate team coordination and identify lacking capabilities.
  2. Establish good practice of structured, coordinated documentation.
Member Discipline Role Responsibility
Zyad Abdelaziz ME Support Design Engineer and Facilitator Managing Conflict, holdings team to the norms and values agreed upon, running meetings smoothly and escalating problems when necessary
Colin Mellett ISE Support Design Engineer and Communications Lead Ensure communication between the team, guide, and customer are running efficiently
Patrick Mathews ME Lead Design Engineer Lead in the design of the diverter and toilet base
Jakob Kobajilo ISE Project Manager and Purchasing Lead Lead project with timeline, staying on track, and ordering/receiving purchases

Team Values and Norms

Purpose

Define the team's expectations of its members and used as the basis for peer reviews.
Accepted Norms of Performance: Peer Assessment Rubric
Value Unsatisfactory Needs Improvement Meets Expectations Exceeds Expectations
Punctual The team member has had one or more unexcused absences or tardy arrivals to a scheduled team activity. The team member is not notifying others of conflicts with meeting times, or has allowed other committments to impede the member's duties to this team. The team member is detracting from the performance of the entire team. The team member has had one or more unexcused absences or tardy arrivals. The individual could and should have done a better job at notifying (in advance) a peer of the absence or tradiness. At the current time, the problem has not caused significant harm to the team, but this behavior needs to improve. It is not unusual for a team member to receive this rating a couple of times during the project. The team member was prompt and present at every team event this week, or any absences were excused in advance. If there was an unexcused absence or tardiness, then the team-mates agreed that the reason disclosed after the fact was indeed unavoidable. For example, a member is in a fender bender on the way to campus, and was unable to contact a team-mate about being late. The absent member caught up with a peer as soon as practical, and informed them of the problem. Not only is the team member always prompt and present, but the member clearly plans ahead for excused absences (such as job trips) and insures that the absence will not adversely affect the team's performance. The member notifies the team of heavy loads and external conflicts (such as exams in other classes) that COULD have an adverse impact on the team, and works with the peers on this team to make sure that the information flow from the member to and from the peers is smooth even in such cases.
Value Unsatisfactory Needs Improvement Meets Expectations Exceeds Expectations
Thorough The team member has not completed the task assigned, or has submitted a response that is clearly insufficient. The work will need to be re-done by another team member in order for the team to move forward. Some of the work may have been done, but it was incomplete. The team member is detracting from the performance of the entire team. The team member made some progress towards the task assigned, but not as much progress as should have been accomplished. The work may be done, but the other team member's have no way of checking the results, because the supporting documentation is incomplete. The team member is getting behind on the tasks that need to be completed. The team member needs to make up the missed work during the next evaluation period. The team member has made solid progress towards the task assigned. The task is complete, and is well done, though it may need some additional work and refinement to be fully complete. The assignment may be incomplete, but the team member has clearly made a good effort towards getting the task done. In retrospect, this task may have been too much for the member to do in the time allocated, so the fact that the task is not done yet is not due to lack of effort by the member. The task has been completed fully, and is in essentially finished form. The other team members can readily check the work submitted since the documentation is so clear. Not only is the work done, but everyone on the team recognizes that the task is complete with little or no need for additional effort.
Value Unsatisfactory Needs Improvement Meets Expectations Exceeds Expectations
Accurate The work completed by the team member is unacceptable and does not meet the basic standards of engineering work. Engineering principles were not applied, or were grossly mis-applied. Basic elements of the engineering task were overlooked. The work completed must be re-done completely. 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. 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. The team member completed the task with virtually no errors or omissions. The work was accurate, and can be easily scaled to other applications or tasks that the team may encounter.
Value Unsatisfactory Needs Improvement Meets Expectations Exceeds Expectations
Professional and Ethical The team member has committed plagiarism, falsified data, ignored their responsibility as an engineer. The team member may have behaved inappropriately at a team event, or in a manner that reflects adversely on the team. The members' actions may cause the entire team to fail. The team member has overlooked some references or consistently fails to cite sources and conduct individual tasks. The team member may have made some off-color remarks or been offensive to a team-mate or other individual. The team member needs to clean up his/her act. The team member behaves responsibly and fully documents sources and collaborators on all work. The team member is a role model for others, and behaves in a professional and ethical fashion even under very trying and difficult circumstances.
Value Unsatisfactory Needs Improvement Meets Expectations Exceeds Expectations
Committed The team member is a burden to the rest of the team. The team member is carrying less than their fair share of the work load. The team member is carrying their fair share of the workload. The team member is carrying more than their fair share of the workload.

Project Plans & Schedules

Purpose

Ensure timely delivery of all required work products, identify prerequisite tasks with owners, ensure special resource needs are met.

Gantt Chart

A Gantt Chart was created to map out the semester and let the team see how many tasks were simultaneous and also give a timeline that tracks how much work has been completed. Besides the milestones set by MSD, the Gantt Chart will not be a set timeline, as there are always expected risks that would have to shift the dates around if necessary. Below are picture examples of what the Gantt Chart looks like as well as links to the current timeline PDF.

MSD1GanntChart.pdf

Team's Project Plan as of 9/11/19

Team's Project Plan as of 9/11/19

Risk Assessment and Growth Curves

Outputs and Destination

Completed form to be revisited at all project reviews.

Updated Files (Currently after Detailed Design Review Gate):

Risk Assessment Excel File

Risk Management First Version

Risk Management First Version

Other Team Resources

Some other resources the team might require in the future

Peer Reviews

Communication

Guide Communication

Team Communication

Project Reviews


Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation